-
b047bb40 · Merge branch 'zj-contributing' into 'master'
- ... and 1 more commit. Compare d9b48fac...b047bb40
accepted
merge request
!14
"Use multi-stage docker builds for Golang.Dockerfile"
at
GitLab.org / Dockerfile
-
d9b48fac · Merge branch 'Golang.Dockerfile-update' into 'master'
- ... and 1 more commit. Compare 2dc63293...d9b48fac
commented on
merge request !16
"Use multi-stage docker builds for Golang-scratch.Dockerfile"
at
GitLab.org / Dockerfile
Because we have to wait for a 3rd party?
commented on
merge request !16
"Use multi-stage docker builds for Golang-scratch.Dockerfile"
at
GitLab.org / Dockerfile
@zj Why WIP?
Possibly. I was using the same base as others use, and didn't investigate if there was something else better.
This seems counter productive
commented on
merge request !14
"Use multi-stage docker builds for Golang.Dockerfile"
at
GitLab.org / Dockerfile
Tested with https://gitlab.com/markpundsack/go-hello-world/container_registry and it works fine on GitLab.com....
commented on
merge request !14
"Use multi-stage docker builds for Golang.Dockerfile"
at
GitLab.org / Dockerfile
Apparently multi-stage support is in Docker 17.05, which is what latest docker:dind has!
commented on
merge request !16
"Use multi-stage docker builds for Golang-scratch.Dockerfile"
at
GitLab.org / Dockerfile
Inspired by http://blog.alexellis.io/mutli-stage-docker-builds/.
commented on
merge request !14
"Use multi-stage docker builds for Golang.Dockerfile"
at
GitLab.org / Dockerfile
Maybe the final build image of all three of these MRs should be based on scratch?