Here’s my advice: the Go toolchain is pretty standardized and pretty easy to get. Glide is a good tool for ensuring that an application package is using specific known versions of its dependencies (up to the limits of dependency tracking in the Go ecosystem). Docker does not need to be part of the ordinary development path.
If you really truly have specialized host-system requirements then Vagrant is a purpose-built tool for building developer virtual machines, and it deals with some of the irritating details like “make the application source code visible inside the container”.
The sequence I’d strongly recommend is:
(0) Most developers don’t need Docker, until and unless they need to deploy a test copy of the whole application.
(1) Developers have their own IDE, local
go binary, libraries, etc.
(2) Developers write code,
go test, get code reviews, repeat, without using Docker at all.
go build a binary of the application.
(4) In a
COPY the application binary into a standard base distribution image (or if you’re brave and built a static binary, into a
FROM scratch image).
(5) Your CI system does the
go build and
docker build automatically to create Docker images.
(If you have very current versions of Docker then you could use a multi-stage build for the last two steps, but from what I can see those versions aren’t widely available in environments like RHEL or cloud CI products.)
Yes, this is the totally normal way to use Docker. Note that this also means that any code change means deleting the old running container, so if you do have persistent data, you need to make sure it’s stored somewhere that will outlive this (IME a database is best, a Docker volume or host directory mount is okay).
This is tricky to set up (read through the forum history, similar questions get asked multiple times a week) and I don’t feel like you really gain much by doing this. You’re also requiring your developers to routinely run commands as root as part of their build sequence which seems like a poor practice from an overall security point of view.
Also, you’ll never deploy your application this way so you’re introducing two different ways to “run the application in Docker” and that will confuse things further.