4 ms·

The image seems to have the code and dependencies copied into it+ `go build` run on it, instead of just copying the built artifact.

• ihsw2 8y ago
  This is an opportunity for enterprising OSS contributors -- by virtue of being written in Go, converting their current Dockerfile to one that uses multi-stage builds should be simple and the resulting image would be as minimal as they come.
  • SEJeff 8y ago
    Example golang multi-stage build: https://github.com/jaegertracing/jaeger/blob/master/cmd/query/Dockerfile https://github.com/jaegertracing/jaeger/blob/master/cmd/quer...
    • Boulth 8y ago
      With the caveat that it doesn't build the app inside container, so the multi stage build is kind of underutilized here.
      • e12e 8y ago
        You almost certainly want to build the app inside a container, but probably not the same container that result from the build. [ed: well maybe not for a simple go project, as go has great cross compilation support. But if there's a bit of Javascript/(s)css/static resource munging - a container with a predictable build environment might become appealing. ]
        • Boulth 8y ago
          Isn't this the purpose of multi stage builds? To have one stage for building it and another, from scratch, to run it?
          • SEJeff 8y ago
            It is one of the purposes, yes. The idea being that you don't need build artifacts in containers which run the application.