Output Dockerfile contents if set to --debug
The Dockerfile we generate won't really work at all outside
of repo2docker. This makes it very clear that these are purely
for debugging purposes.
MODIFY
repo2docker/app.py
repo2docker/app.py
@@ -145,8 +145,8 @@ class Repo2Docker(Application):
)
argparser.add_argument(
- '--print-dockerfile',
- help="Print dockerfile contents to stdout",
+ '--debug',
+ help="Turn on debug logging",
action='store_true',
)
@@ -182,6 +182,9 @@ class Repo2Docker(Application):
def initialize(self):
args = self.get_argparser().parse_args()
+ if args.debug:
+ self.log_level = logging.DEBUG
+
self.load_config_file(args.config)
if os.path.exists(args.repo):
@@ -223,7 +226,6 @@ class Repo2Docker(Application):
self.run = args.run
self.json_logs = args.json_logs
- self.print_dockerfile = args.print_dockerfile
self.build = args.build
if not self.build:
# Can't push nor run if we aren't building
@@ -316,8 +318,7 @@ class Repo2Docker(Application):
picked_buildpack = bp
break
- if self.print_dockerfile:
- self.log.info(picked_buildpack.render(), extra=dict(phase='building'))
+ self.log.debug(picked_buildpack.render(), extra=dict(phase='building'))
if self.build:
self.log.info('Using %s builder\n', bp.name, extra=dict(phase='building'))

Output Dockerfile contents if set to --debug

The Dockerfile we generate won't really work at all outside
of repo2docker. This makes it very clear that these are purely
for debugging purposes.