top | item 14338223 Multi-Stage Docker Builds for Creating Tiny Go Images 4 points| transitorykris | 8 years ago |medium.com | reply 4 comments order hn newest [+] [-] awinter-py|8 years ago|reply Holy crap, hadn't heard of this. Sounds like it's merged to master and coming down the pipe for 17.05. https://docs.docker.com/engine/userguide/eng-image/multistag...This solves a major pain point for many people working w/ dockerfiles. [+] [-] transitorykris|8 years ago|reply Yep! Building smaller images is just one part of the story. There are other pains this helps with, the biggest for me delivering images with no unnecessary artifacts (uncompiled code, ssh keys when `go get`ing private repos, ...) load replies (1) [+] [-] tqh|8 years ago|reply For Go (as it is statically linked) you can use FROM SCRATCH. It's faster, smaller, easier. https://blog.docker.com/2016/09/docker-golang/
[+] [-] awinter-py|8 years ago|reply Holy crap, hadn't heard of this. Sounds like it's merged to master and coming down the pipe for 17.05. https://docs.docker.com/engine/userguide/eng-image/multistag...This solves a major pain point for many people working w/ dockerfiles. [+] [-] transitorykris|8 years ago|reply Yep! Building smaller images is just one part of the story. There are other pains this helps with, the biggest for me delivering images with no unnecessary artifacts (uncompiled code, ssh keys when `go get`ing private repos, ...) load replies (1)
[+] [-] transitorykris|8 years ago|reply Yep! Building smaller images is just one part of the story. There are other pains this helps with, the biggest for me delivering images with no unnecessary artifacts (uncompiled code, ssh keys when `go get`ing private repos, ...) load replies (1)
[+] [-] tqh|8 years ago|reply For Go (as it is statically linked) you can use FROM SCRATCH. It's faster, smaller, easier. https://blog.docker.com/2016/09/docker-golang/
[+] [-] awinter-py|8 years ago|reply
This solves a major pain point for many people working w/ dockerfiles.
[+] [-] transitorykris|8 years ago|reply
[+] [-] tqh|8 years ago|reply