Supported tags and respective
Where to file issues:
the Docker Community
Supported Docker versions:
the latest release (down to 1.6 on a best-effort basis)
What is Go?
Go (a.k.a., Golang) is a programming language first developed at Google. It is a statically-typed language with syntax loosely derived from C, but with additional features such as garbage collection, type safety, some dynamic-typing capabilities, additional built-in types (e.g., variable-length arrays and key-value maps), and a large standard library.
How to use this image
Start a Go instance in your app
The most straightforward way to use this image is to use a Go container as both the build and runtime environment. In your
Dockerfile, writing something along the lines of the following will compile and run your project:
FROM golang:1.8 WORKDIR /go/src/app COPY . . RUN go-wrapper download # "go get -d -v ./..." RUN go-wrapper install # "go install -v ./..." CMD ["go-wrapper", "run"] # ["app"]
You can then build and run the Docker image:
$ docker build -t my-golang-app . $ docker run -it --rm --name my-running-app my-golang-app
go-wrapper run includes
set -x so the binary name is printed to stderr on application startup. If this behavior is undesirable, then switching to
CMD ["app"] (or
CMD ["myapp"] if a Go custom import path is in use) will silence it by running the built binary directly.
Compile your app inside the Docker container
There may be occasions where it is not appropriate to run your app inside a container. To compile, but not run your app inside the Docker instance, you can write something like:
$ docker run --rm -v "$PWD":/usr/src/myapp -w /usr/src/myapp golang:1.8 go build -v
This will add your current directory as a volume to the container, set the working directory to the volume, and run the command
go build which will tell go to compile the project in the working directory and output the executable to
myapp. Alternatively, if you have a
Makefile, you can run the
make command inside your container.
$ docker run --rm -v "$PWD":/usr/src/myapp -w /usr/src/myapp golang:1.8 make
Cross-compile your app inside the Docker container
If you need to compile your application for a platform other than
linux/amd64 (such as
$ docker run --rm -v "$PWD":/usr/src/myapp -w /usr/src/myapp -e GOOS=windows -e GOARCH=386 golang:1.8 go build -v
Alternatively, you can build for multiple platforms at once:
$ docker run --rm -it -v "$PWD":/usr/src/myapp -w /usr/src/myapp golang:1.8 bash $ for GOOS in darwin linux; do > for GOARCH in 386 amd64; do > go build -v -o myapp-$GOOS-$GOARCH > done > done
golang images come in many flavors, each designed for a specific use case.
This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of. This tag is based off of
buildpack-deps is designed for the average user of docker who has many images on their system. It, by design, has a large number of extremely common Debian packages. This reduces the number of packages that images that derive from it need to install, thus reducing the overall size of all images on your system.
This image is based on the popular Alpine Linux project, available in the
alpine official image. Alpine Linux is much smaller than most distribution base images (~5MB), and thus leads to much slimmer images in general.
This variant is highly recommended when final image size being as small as possible is desired. The main caveat to note is that it does use musl libc instead of glibc and friends, so certain software might run into issues depending on the depth of their libc requirements. However, most software doesn't have an issue with this, so this variant is usually a very safe choice. See this Hacker News comment thread for more discussion of the issues that might arise and some pro/con comparisons of using Alpine-based images.
To minimize image size, it's uncommon for additional related tools (such as
bash) to be included in Alpine-based images. Using this image as a base, add the things you need in your own Dockerfile (see the
alpine image description for examples of how to install packages if you are unfamiliar).
ONBUILD image variants are deprecated, and their usage is discouraged. For more details, see docker-library/official-images#2076.
onbuild variant is really useful for "getting off the ground running" (zero to Dockerized in a short period of time), it's not recommended for long-term usage within a project due to the lack of control over when the
ONBUILD triggers fire (see also
Once you've got a handle on how your project functions within Docker, you'll probably want to adjust your
Dockerfile to inherit from a non-
onbuild variant and copy the commands from the
Dockerfile (moving the
ONBUILD lines to the end and removing the
ONBUILD keywords) into your own file so that you have tighter control over them and more transparency for yourself and others looking at your
Dockerfile as to what it does. This also makes it easier to add additional requirements as time goes on (such as installing more packages before performing the previously-
This image is based on Windows Server Core (
microsoft/windowsservercore). As such, it only works in places which that image does, such as Windows 10 Professional/Enterprise (Anniversary Edition) or Windows Server 2016.
For information about how to get Docker running on Windows, please see the relevant "Quick Start" guide provided by Microsoft:
View license information for the software contained in this image.
We try to sync the golang image channel unto our RedHat Satellite Server, but the sync breaks because of a pulp error that misses a linked image layer:
PLP0037: Content import of /firstname.lastname@example.org/3d009b5c-b9f2-4d5a-a733-1c69cf85f79a/sha256:de5064718b3f2749727c8b5ffddf2da7698189277afe0df6fc0a57ad573bca0f failed - must be an existing file.
According to the RedHat Support this is an inconsistency in the golang channel.
I have been having trouble getting cover to install using 1.3.0 build. I keep getting the message to install it but the install command does not work.
go tool: no such tool "cover"; to install:
go get code.google.com/p/go.tools/cmd/cover
godep: go exit status 3
Has anyone been able to get "onbuild" to work with a proxy?
I've added my proxies to the Dockerfile (ENV http_proxy http://xxx.xxx:xxx), but the 'RUN go get' step still fails to connect through the set proxy.
I am super newb to docker containers and go. We are building a go backend and Vue front end. Would it be best to build my own container, Use golang:onbuild, or use golang:alpine? I can't seem to get the golang:onbuild to even work as it just errors out with can't load package: package app: no buildable Go source files in /go/src/app. We have our files set up with a server and client folder so not sure how that works with the go folder that has src, bin, github.com... Our go files are in the server folder.
golang:1-nanoserver cannot be pulled:
$ docker pull golang:1-nanoserver 1-nanoserver: Pulling from library/golang 5496abde368a: Downloading 94b4ce7ac4c7: Downloading 12ba288c0d1d: Download complete 66aabf8dca12: Download complete 3844df32288b: Download complete 5158e3477b73: Download complete 3e5e2bb6eccb: Download complete 6dd062b023f9: Download complete 03042fad0011: Download complete 5e6024ecc84e: Download complete unknown blob
The right way compile your app with golang docker image
docker run --rm --name go-build -v /data/www/lolipos:/go/src/lolipos -w /go/src/lolipos golang sh -c " go get -u -v -d ... ; go build -v"
Is there any chance of a golang:windowsservercore image? :-)
The instructions for cross-compilation did not work until I replaced
I prefer using alpine, but came across an issue using
-race flag on
build. I receive the following error:
# runtime/race race_linux_amd64.syso: In function `__sanitizer::InternalAlloc(unsigned long, __sanitizer::SizeClassAllocatorLocalCache<__sanitizer::SizeClassAllocator32<0ul, 140737488355328ull, 0ul, __sanitizer::SizeClassMap<17ul, 64ul, 14ul>, 20ul, __sanitizer::TwoLevelByteMap<32768ull, 4096ull, __sanitizer::NoOpMapUnmapCallback>, __sanitizer::NoOpMapUnmapCallback> >*)': gotsan.cc:(.text+0x1681): undefined reference to `__libc_malloc' race_linux_amd64.syso: In function `__sanitizer::ReExec()': gotsan.cc:(.text+0xd937): undefined reference to `__libc_stack_end' race_linux_amd64.syso: In function `__sanitizer::InternalFree(void*, __sanitizer::SizeClassAllocatorLocalCache<__sanitizer::SizeClassAllocator32<0ul, 140737488355328ull, 0ul, __sanitizer::SizeClassMap<17ul, 64ul, 14ul>, 20ul, __sanitizer::TwoLevelByteMap<32768ull, 4096ull, __sanitizer::NoOpMapUnmapCallback>, __sanitizer::NoOpMapUnmapCallback> >*)': gotsan.cc:(.text+0x5ec8): undefined reference to `__libc_free' collect2: error: ld returned 1 exit status
Based on this issue it's not something that can be easily fixed.
If you are using the suggested structure from "Test your installation", this should work for you:
docker run --rm -v "$GOPATH":/work -e "GOPATH=/work" -w /work/src/github.com/<username>/<repository> golang:alpine go build -v