In this post, we created an image that deals with go-based containers. When tagging it golang, building works out of the box for most Dockerfiles.
Now that golang has been ported to s390x, we can look at this again, creating a golang image that bases on golang rather than gccgo:
Showing posts with label gccgo. Show all posts
Showing posts with label gccgo. Show all posts
Sunday, January 31, 2016
Friday, July 31, 2015
Portability Series: A Go Environment
Previously we looked at the portability of container setups. One of the observations is that a lot of containers are based on a Go environment -- take swarm or the registry. On x86, that usually means golang, but we have gccgo on s390. Let's see, how we can deal with this difference.
Subscribe to:
Posts (Atom)