Follow-up fixes on multi-stage moby's Dockerfile#36425
Follow-up fixes on multi-stage moby's Dockerfile#36425thaJeztah merged 2 commits intomoby:masterfrom
Conversation
Signed-off-by: Vincent Demeester <vincent@sbr.pm>
62fc030 to
4ef3925
Compare
|
CI failed. On windows: I have no idea what it means, though. In |
Dockerfile
Outdated
There was a problem hiding this comment.
Wondering if we should use:
ARG GO_VERSION=1.9.3
FROM golang:$GO_VERSIONWhich would also allow testing on different versions if we'd want to
There was a problem hiding this comment.
Actually this means we can't test go rc's
There was a problem hiding this comment.
Should work, Docker Hub also pushes images for rc's
There was a problem hiding this comment.
@cpuguy83 to test RC's we could also "temporarly" refer to other images we build too, couldn't we ? 👼
There was a problem hiding this comment.
You can't do anything out of the norm! ;)
Actually didn't realize there were rc's on hub. That's great.
There was a problem hiding this comment.
We have a long tradition of pushing the RCs too: 😇
$ docker-hub-list-tags.sh library/golang | grep rc | grep -vE 'onbuild|wheezy|windowsservercore|nanoserver|cross'
rc
1.10-rc
1.10rc2
rc-stretch
1.10-rc-stretch
1.10rc2-stretch
rc-alpine
1.10-rc-alpine
1.10rc2-alpine
rc-alpine3.7
1.10-rc-alpine3.7
1.10rc2-alpine3.7
1.10rc1
1.10rc1-alpine
1.10rc1-alpine3.7
1.10rc1-stretch
1.9-rc-alpine
1.9rc2-alpine
rc-alpine3.6
1.9-rc-alpine3.6
1.9rc2-alpine3.6
1.9-rc
1.9rc2
1.9-rc-stretch
1.9rc2-stretch
1.9rc1-alpine
1.9rc1-alpine3.6
1.9rc1
1.9rc1-stretch
1.8-rc-alpine
1.8rc3-alpine
1.8-rc-stretch
1.8rc3-stretch
1.8-rc
1.8rc3
1.8rc2-alpine
1.8rc2
1.8rc1
1.8rc1-alpine
1.7rc6-alpine
1.7rc6
1.7rc5-alpine
1.7rc5
1.7rc4-alpine
1.7rc4
1.7rc3
1.7rc3-alpine
1.7rc2-alpine
1.7rc2
1.7rc1-alpine
1.7rc1
1.6rc2-alpine
1.6rc2
1.6rc1-alpine
1.6rc1
1.5rc1
1.4rc2
1.4rc1(back to Go 1.4rc1 -- docker-library/golang#26; 2014! 😄)
Dockerfile
Outdated
There was a problem hiding this comment.
Guess it doesn't make a difference for us, but the order is slightly different in the official Golang images (just leaving it here);
ENV GOPATH /go
ENV PATH $GOPATH/bin:/usr/local/go/bin:$PATH|
Except CI failures. :( |
|
Oh windowsRS1 failure is real... the I can either keep that |
|
I think you can do |
Dockerfile
Outdated
There was a problem hiding this comment.
Actually, just realised that we use the GO_VERSION env-var as well in the scripts to generate the "builder" images;
There was a problem hiding this comment.
ohhh 😓 ok I think I have an idea of what to do 👼
Signed-off-by: Vincent Demeester <vincent@sbr.pm>
4ef3925 to
572cb66
Compare
Codecov Report
@@ Coverage Diff @@
## master #36425 +/- ##
=========================================
Coverage ? 34.95%
=========================================
Files ? 613
Lines ? 45375
Branches ? 0
=========================================
Hits ? 15859
Misses ? 27422
Partials ? 2094 |
runtime-devis already base ongolang)golangofficial image as base (instead ofdebian:stretchand installing go manually)This is gonna affect the cache quite a lot (because well, it's updating the base image for almost everything 😅 )
Signed-off-by: Vincent Demeester vincent@sbr.pm