News for hackers. Stuff that matters.
Re:Show HN: Jackal – XMPP server in Go by r_venkat on Tuesday May 08, 2018 @10:37AM (#17021164)
The image seems to have the code and dependencies copied into it+ `go build` run on it, instead of just copying the built artifact.
Re:Show HN: Jackal – XMPP server in Go by ihsw2 on Tuesday May 08, 2018 @11:20AM (#17021525)
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.
Re:Show HN: Jackal – XMPP server in Go by SEJeff on Tuesday May 08, 2018 @11:39AM (#17021724)
Re:Show HN: Jackal – XMPP server in Go by Boulth on Tuesday May 08, 2018 @12:10PM (#17022023)
With the caveat that it doesn't build the app inside container, so the multi stage build is kind of underutilized here.
Re:Show HN: Jackal – XMPP server in Go by e12e on Tuesday May 08, 2018 @12:43PM (#17022347)
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. ]

Re:Show HN: Jackal – XMPP server in Go by Boulth on Tuesday May 08, 2018 @01:03PM (#17022527)
Isn't this the purpose of multi stage builds? To have one stage for building it and another, from scratch, to run it?
Re:Show HN: Jackal – XMPP server in Go by SEJeff on Tuesday May 08, 2018 @01:31PM (#17022779)
It is one of the purposes, yes. The idea being that you don't need build artifacts in containers which run the application.