Dockerfile: Add missing GOPROXY build argument #843
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Previously, commit 102616b tried to expose GOPROXY env var from developer environment by specifying it as environment variable or build argument to container build process. But using --build-arg to container build command would require the same to be referenced inside Dockerfile/Containerfile so that the following warning can be avoided: [Warning] one or more build args were not consumed: [GOPROXY] Signed-off-by: Anoop C S <anoopcs@cryptolab.net>
anoopcs9
added
the
no-API
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Previously, commit 102616b tried to expose GOPROXY env var from developer environment by specifying it as environment variable or build argument to container build process. But using --build-arg to container build command would require the same to be referenced inside Dockerfile/Containerfile so that the following warning can be avoided: