-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Use multi-stage Dockerfile instead of building using host's Go binary #167
Comments
Is the idea behind this to ensure that the build environment is same for everyone and not dependent on user's local tools? |
Yeah. It's a more reproducible build and reduces the use of arbitrary bash scripts. |
Taking on this one. |
Is it desirable to use a scratch image for the final result?
|
Any updates on this? I am setting up CI for a new project and it would be great if I could utilize the automated build build of Quay.io directly, instead of using something like Travis as an intermediate stage for building the image. |
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
Stale issues rot after 30d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle rotten |
Rotten issues close after 30d of inactivity. Reopen the issue by commenting /close |
@openshift-bot: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Something like https://github.com/coreos/dex/blob/master/Dockerfile
The text was updated successfully, but these errors were encountered: