support 32-bit arm on dockerhub?

[snpz]

support 32-bit arm on dockerhub?

[gaul]

Currently the automated Docker push via CI is broken #479. Before a contributor added ARM64 support, this worked for x86-64. Ideally I would like to repair this if someone can tell me what is broken. Then I would be happy to accept a PR to include 32-bit ARM as part of the automated push. I don't have much background in Docker so this will likely need to be a contribution from the community.

[snpz]

Thanks for your swift reply. I'm not deep into Docker myself but just took some time to see what could be the issue.
So I had a look in your ci-file and the errors when trying to copy the image from the github-registry to docker.io.

The error is pretty explanatory: https://github.com/gaul/s3proxy/actions/runs/7040721261/job/19162231024#step:10:27
Failed to get manifest docker.io/library/master:latest: Unauthorized [http 401]: {"errors":[{"code":"UNAUTHORIZED","message":"authentication required","detail":[{"Type":"repository","Class":"","Name":"library/master","Action":"pull"}]}]}

I'd say the Url is not correct and should include the path to your repository.

I just tried this locally with my (private) docker repo and those commands did the trick for me:

~$ ./regctl image copy ghcr.io/gaul/s3proxy/container:master docker.io/steffenpe/testrepo:master
Manifests: 3/3 | Blobs: 206.795MB copied, 0.000B skipped | Elapsed: 59s
docker.io/steffenpe/testrepo:master

In ci-main.yml I see the following:
for line in $CONTAINER_DEST_TAGS; do echo working on "$line"; /tmp/regctl image copy $SOURCE_CONTAINER $line; done

The failing step in CI outputs the value of $line and it is:
working on ghcr.io/gaul/s3proxy/container:master

I guess regctl uses only the tag from that string and builds up the path itself which results in
docker.io/library/master:latest instead of docker.io/library/andrewgaul/s3proxy:master which should be the correct one.

So I think you need to get the $tagname from $line and concat it to docker.io/andrewgaul/s3proxy:$tag.
I'm not deep into linux either, but I will see if I can come up with something.

small addition: maybe it would also make sense to use a more recent version of regctl instead of 0.3.5 which is currently used.
The current one is v0.5.6.