-
Notifications
You must be signed in to change notification settings - Fork 238
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
dockerfile: update builder image to golang v1.18 #836
dockerfile: update builder image to golang v1.18 #836
Conversation
/assign @ArangoGutierrez |
@@ -2,7 +2,7 @@ ARG BASE_IMAGE_FULL | |||
ARG BASE_IMAGE_MINIMAL | |||
|
|||
# Build node feature discovery |
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.
Maybe it's better to specify just 1.18
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.
Thanks @e0ne for the suggestion. The reason we've been using "fixed" golang versions has been reproducibility but I realized it doesn't make much sense in master. Changed as you suggested.
539ceb0
to
586fc81
Compare
/retitle dockerfile: update builder image to golang v1.18 |
Switch over to the "non-point-release" version of the image. Now we always use the latest patch version of golang with latest security fixes, for example, without the need to manually bump the version after every point release. This patch also makes the builder image configurable through a Makefile variable. For reproducible builds we should used fixed point-release versions in release-brances.
586fc81
to
8d56634
Compare
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.
LGTM, thanks for addressing my commments
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: e0ne, marquiz The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
ping @ArangoGutierrez |
/cc zvonkok |
Time for 1.19 while we're at it? |
/lgtm |
Let's do that separately. |
Switch over to the "non-point-release" version of the image. Now we
always use the latest patch version of golang with latest security
fixes, for example, without the need to manually bump the version after
every point release.
This patch also makes the builder image configurable through a Makefile
variable.
For reproducible builds we should used fixed point-release versions in
release-brances.