feature request: docker build interactive

[senthilnayagam]

when building with docker build, occasionally builds fail and the image is not saved

common problems while writing Dockerfile include, missing dependencies, config changes, new package paths

currently what I do is check all the images and run the image in bash and correct it and then commit the image

there can be a interactive version of build where if interactive mode is on, if the build fails it goes into the bash console and that line can be fixed and subsequent commands can be run

something like
sudo docker build -t="projectname" . -i -t /bin/bash

[crosbymichael]

I think a simple sudo docker build -t . that allows stdin would help a lot when building images. Django admin anyone?

[Thermionix]

currently trying to write a dockerfile for postfix+dovecot & being able to input the hostname would make life good

[jpetazzo]

In that specific case, I would suggest to hard-code a placeholder hostname (e.g. @@HOSTNAME@@); then, when starting the container, you would actually start a wrapper script, which would find the real hostname from the environment (with the -e option to docker run), and use sed or rpl to change @@HOSTNAME@@ to the value of the environment variable.

Would that work for you?

[Thermionix]

I'm thinking mostly for sharing dockerfiles https://raw.github.com/Thermionix/Dockerfiles/master/mail-stack-delivery/Dockerfile

[crosbymichael]

Actually with the new trusted builds and different builds systems for Dockerfiles we do not want stdin because it can produce an inconsistent result. Every time you run docker build you want the same result to be produced. Variables and stdin for the build process is not something that we want.

If you want to discuss alternatives to a specific issue please join IRC or post on the user mailing list. You may find more help there.