I have no idea what golang-crossbuild uses, but it appears to be Debian based, so, even despite that fact, it's going to be hilariously too recent, so, it'll just create plain unusable binaries ;).

You should be able to use koxtoolchain on pretty much anything, though, so, basically anything that works for you as a base can be tweaked to include a usable TC.

I have no idea what golang-crossbuild uses, but it appears to be Debian based, so, even despite that fact, it's going to be hilariously too recent, so, it'll just create plain unusable binaries ;).

Thanks for the heads-up on that. It's a no-go then.

Ah, finally found the comment from @pgaskin with a starting point Dockerfile. I knew he had posted it somewhere...

Might polish it up, chuck it on Github, and push an image to Docker Hub, or the new Github container registry perhaps.

This is pretty simple to do no matter which approach you take, although adding Go to an existing image will probably be the shortest.

or the new Github container registry perhaps

The main issue with that one is it wants authentication to pull images.

The main issue with that one is it wants authentication to pull images.

Really? From what I've read, that applies to GitHub packages. However, from what I've read, the container registry that was recently announced allows public images to be pulled anonymously.

Oh, that's new. I'll probably switch most references to NickelTC to it then.