Build for ARM Architectures about docker-volume-backup HOT 9 CLOSED

Building for ARM sounds like a great idea, although I don't know too much about how to do it.

From what I understand there are two options:

1. Use buildx
2. Add a second job to the CircleCI setup that runs on ARM hardware (although I would assume this is arm64 only)

I'd be happy to look into this, but it might take a while. If you wanna give it a go in the meantime, I am happy to review and merge PRs.

Relevant place for doing this is probably

from docker-volume-backup.

Ok, cool, I can take a look at it sometime this week.

I don't know anything about CircleCI, so I have no idea what kind of ARM architectures they support. I know you can do this on any host using QEMU through buildx. I've done that on Github Actions, so it's probably the approach I'll try to go with.

from docker-volume-backup.

I've done that on Github Actions, so it's probably the approach I'll try to go with.

If switching to GitHub actions helps you get this set up, I'd be totally fine with ditching CircleCI here. I guess we can push to Docker Hub from anywhere.

Thank you!

from docker-volume-backup.

I just had some time to look into this myself and got buildx working on CircleCI https://github.com/offen/docker-volume-backup/compare/multiarch

There are however some issues still that I currently don't know how to resolve:

• the mc MinIO client is only available for arm64 so this is a hard limit for what this repo can build
• the arm64 build never passes, but seems to fail at different stages. Sometimes it fails to run apk add, sometimes it fails later when downloading the mc executable (sth along the lines of "connection reset by peer"). I assume this is some Networking issue caused by Docker in Docker in Docker (yes, this is what is happening) or similar

It would be interesting to know if:

• does this build successfully in GitHub actions?
• does this build successfully when "unboxed" in CircleCI and run in a machine executor instead of a Docker one?

from docker-volume-backup.

Another very strange detail here: when using an http (instead of https) URL for downloading the MinIO client in the Dockerfile I can get the arm64 build to pass sometimes (unless it fails earlier).

from docker-volume-backup.

This is somehow related to networking and ca-certificates, but I don't really understand how.

When I build this locally for arm64 I will always be able to run the apk commands in the Dockerfile correctly, but downloading mc will also fail in case it's trying to use https. When using http I can successfully build an arm64 image locally.

In case anyone knows where this is coming from, I'm happy about any pointers.

from docker-volume-backup.

Upstream issue is here docker/buildx#660

from docker-volume-backup.

Ok, this required some serious voodoo as per: https://gitlab.alpinelinux.org/alpine/aports/-/issues/12406 but it seems to be working for arm64 now and v1.4.0 is published to Docker Hub, supporting multiple architectures.

If anyone has an idea how to make this work for arm/v7 et al too, I would be happy to learn about your ideas.

from docker-volume-backup.

arm/v7 works when the build compiles mc from source. v1.5.0 is now available for amd64, arm64 and arm/v7.

from docker-volume-backup.