-
Notifications
You must be signed in to change notification settings - Fork 18.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Proposal: TO instruction for Dockerfile #7655
Comments
Closing as dup of #5603 |
@cmfatih Please explain how this is different other than the keyword that's being used? |
And also #2740 |
Both 5603 and 2740 are not relevant to this proposal. |
Hi @cmfatih - can you explain why they are not relevant and what's different about your proposal from the |
Let me re-open since I shouldn't have closed it without someone else reviewing as well. |
@jamtur01 & @cpuguy83 : Yup... I'm wrong this is dup. I just see the last comment; #5603 (comment)
This is exactly what I need... @cpuguy83 : You can shut me down now :) |
Ok, thanks @cmfatih |
Dockerfile's multiple images support could be more useful. We can use
TO
instruction for tagging images.My current approach;
docker build -t="ubuntu-custom" path/to/Dockerfile
docker build -t="nodejs" path/to/Dockerfile // nodejs has instruction FROM ubuntu-custom
docker build -t="my-app" path/to/Dockerfile // myapp has instruction FROM nodejs
if we have a
TO
instruction then it would be like (only one Dockerfile);docker build -t="doesn't matter" path/to/Dockerfile
docker run images
The text was updated successfully, but these errors were encountered: