[pknopf]

The base docker images (https://github.com/godarch/distributions) only supports x86_64. Docker images have support for having multiple embedded rootfs tarballs for multiple platforms, but it gets complicated. Maybe in the future.

Also, you have to build your recipes on the same target arch that you are going to deploy to. Irrelevant to your question, but something to note.

[Vaelatern]

I'm having a .... not fun time updating darch to the latest version. Does your makefile still require git, or can I kill that code?

[pknopf]

You can remove the git stuff, as long as you are not building containerd and runc as well.

What issues are you running into? The AUR and VoidLinux package don't have an issue. Skype (paul.knopf1) me?

[Vaelatern]

Why does a go get pull in docker and everything else?

I'm trying to clean up the Void package to make it more maintainable.

[pknopf]

Darch isn't "go get"-able. Things need to be vendored and you'll need a certain version of containerd and runc (which isn't "go get"-able either).

Are you having a problem with the Void package script? The go build template for Void is very naive, I wouldn't use it. It uses symlinks which doesnt place nice with vendoring tools. Things will be a lot smoother when vgo is done and their template is updated accordingly.

[Vaelatern]

Except that the makefile really depends on submodule updates and other mechanisms that require a git clone (hard on the build servers) instead of a tarball that can be cached and checksummed.

[pknopf]

Yeah, when I added the package, I told them the next version will not require vendoring and can be built without git. The next version will do this.