-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Add a multi-stage Dockerfile #871
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we replace existing docker with this for clean view? (:
We absolutely can but each time I tried to propose this I got "we prefer to build it outside docker and package it afterward" |
Ah, my bad did not look closer. So I think this is quite useful and keeping it here seems ok as well. We have 2 options. Leave 2 Dockerfiles, but worth to name them better? For example Otherwise we can do single multi stage with 3 images. 2 as you created, and 3rd with just copy without |
I don't understand the purpose of a multi stage Dockerfile if the last stage does not copy the build results of the previous stages. As for the name I'd keep it like that I don't like the |
Sure, let's do that (: So maybe at least |
Some of them has, rest you can explicitly run using |
That I can do. |
Signed-off-by: Sylvain Rabot <s.rabot@lectra.com>
2988876
to
d051c3e
Compare
Thanks! Awesome. |
This makes it easy to build a thanos image without a proper dev env set up.
Also allows to build images using quay.io or docker hub services.