You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is something the daemon-side builder definitely cannot do.
Let the user execute a single step at a time at the shell prompt, with each step appended to the Dockerfile, if successful. After each step it is possible to examine the image by starting a shell in a temporary container or actually start the container. If not satisfied, you can pop the last step or steps and try again. Just recall the command in your shell history, edit it and retry.
When done, you have both an image and the Dockerfile used to build it. You can also see an annotated version with information like the time used by the step, layer size, etc.
Except for special commands like undo and examine image, the syntax is simply "dockramp" followed by a Dockerfile command (single quoted, if necessary).
The usefulness of this depends on not using any commands not backward compatible with standard Dockerfile, of course.
The text was updated successfully, but these errors were encountered:
This is something the daemon-side builder definitely cannot do.
Let the user execute a single step at a time at the shell prompt, with each step appended to the Dockerfile, if successful. After each step it is possible to examine the image by starting a shell in a temporary container or actually start the container. If not satisfied, you can pop the last step or steps and try again. Just recall the command in your shell history, edit it and retry.
When done, you have both an image and the Dockerfile used to build it. You can also see an annotated version with information like the time used by the step, layer size, etc.
Except for special commands like undo and examine image, the syntax is simply "dockramp" followed by a Dockerfile command (single quoted, if necessary).
The usefulness of this depends on not using any commands not backward compatible with standard Dockerfile, of course.
The text was updated successfully, but these errors were encountered: