Compiling Go Binaries with Alpine Docker

So, previously, I discussed how to setup a Self Compiling Go Docker Container. One of the issues I came across while doing so was getting reflex compiled correctly for the alpine environment. I’m quoting directly from this repo: Because alpine linux and therefor gliderlabs/alpine docker containers use musl instead gnu libc, your golang binaries build using libc will not work on alpine. You can further read up on wikipedia on what musl is.

Self Compiling Go with Docker

Imagine a self contained development environment that could detect that there’s a file change on my file system, kill an existing go binary, rebuild the go binary, and then, launch a new process. Introduction I believe that setting up a docker container that self compiles my Go source upon changes within a local development environment will assist myself and colleagues iterate faster. I am a remote engineer with a mix of other disciplines on my team that are new to the language.

Brackets & Go Development

As I dive more and more into Go, I’ve been playing around with different editors. By default, I tend to stick with Sublime Text just due to speed and having an IDE that doesn’t get in my way. I’ve been playing around with Atom, Limetext, etc. More recently, I opted to give Brackets another go and I’m actually kind of surprised. David S├ínchez i Gregori has done an excellent job with Brackets-Go-IDE go brackets plug-in.

Go Beginnings

In attempts to become a polyglot, I’ve been learning a language outside of my day job language (CFML). Aaron Greenlee suggested I take a look at Go Programming Language. So, I’ve been poking at it with a stick here and there. Every growing links I find useful: http://golang.org https://gobyexample.com http://goinggo.net/ http://golang-examples.tumblr.com http://go-book.appspot.com http://dave.cheney.net/resources-for-new-go-programmers Crazy fun tcp/websocket talk - http://vimeo.com/53221560