mirror of
https://github.com/eduardolat/pgbackweb.git
synced 2026-04-25 05:35:57 +03:00
[GH-ISSUE #18] Support for arm64 images #18
Labels
No labels
bug
confirmed next step
duplicate
enhancement
help wanted
in progress
in progress
pull-request
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/pgbackweb#18
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @arminus on GitHub (Aug 4, 2024).
Original GitHub issue: https://github.com/eduardolat/pgbackweb/issues/18
First of all, great idea and looking forward to the planned features!
Since my always-on box at home is a Pi4, I've tried to test this there by extending your Dockerfile for arm64, see here. Cross built the image (on a faster amd64) like so:
Then, to bypass a docker registry for now, copied the image to the Pi4 and loaded it with
Works like a charm.
In case you're interested, I'd create a PR, maybe I also have time to checkout how to set this up in a github build pipeline for arm64 but I haven't done this before so no promises ;-)
@eduardolat commented on GitHub (Aug 4, 2024):
Great! It can be very useful, just make sure your PR doesn't add too much complexity to the project, as it's important to keep it as simple as possible.
Thanks for considering contributing to the project.
@arminus commented on GitHub (Aug 5, 2024):
No complexity, it's just platform specific wgets in your Dockerfile, see https://github.com/eduardolat/pgbackweb/pull/21
I see no github pipeline for how you build and publish your Docker image, so I can't automate that I'm afraid.
@ykrasik commented on GitHub (Aug 12, 2024):
+1 on this, please
@ThisIsBenny commented on GitHub (Sep 5, 2024):
+1
@eduardolat commented on GitHub (Sep 7, 2024):
Thanks @arminus for your great help.
Since you opened your pr, there have been many changes to the Dockerfiles, the base image has been changed, dependencies have been added, and many other things.
However, I have taken the changes proposed in your pr #21 and adapted them to the new Dockerfiles.
I have also included a script that checks that the dependencies are working correctly and I have added it to the github actions tests workflow.
All that is left is to add a github action to automatically publish the image in each release.
Everything is working perfectly and this will be published in the next release, thanks for your help and thanks to everyone for the interest in the project 🍻
@eduardolat commented on GitHub (Sep 8, 2024):
This has been published in the v0.3.0 release https://github.com/eduardolat/pgbackweb/releases/tag/0.3.0
@ThisIsBenny commented on GitHub (Sep 9, 2024):
I got the error:
exec user process caused: exec format errorWhich usually happens when it is not an ARM64 image.
Is the image working for some one?
@eduardolat commented on GitHub (Sep 9, 2024):
hey @ThisIsBenny, can you try to pull the latest version with this command?
docker pull --platform=linux/arm64 eduardolat/pgbackweb:0.3.0And then explicitly set in your compose file the version of your image to
@ThisIsBenny commented on GitHub (Sep 9, 2024):
I have used it with my Raspberry PI Kubernetes Cluster, why i'm not able to specify the platform manually. But I have used the 0.3.0 Tag and also tried with the SHA hash of the Arm image like 0.3.0@sha....
@eduardolat commented on GitHub (Sep 9, 2024):
Can you please try (just for test purposes) with the docker compose in the README.md?
@arminus commented on GitHub (Sep 11, 2024):
then compose
(note: 2 tags are illegal syntax)
does not work, still getting exec format error.
I assume the Manifest for the images is wrong or missing:
Normally (with all other images I run on my Pi4), I don't have to explicitly set the platform when pulling, docker figures this out on its own if the images are configured properly (but I haven't built multiplatform images myself yet, so I can only guess here)
@electric-m commented on GitHub (Nov 6, 2024):
Same issue for me here an a Hetzner ARM VPS.
Explicitly defined pulled an d defined the 0.3.0. tag.
@eduardolat commented on GitHub (Nov 6, 2024):
You are totally right! the fix is on the way on the develop branch, will be included in next release
@electric-m commented on GitHub (Nov 6, 2024):
Ok, Great!
@electric-m commented on GitHub (Nov 29, 2024):
Can I already use ARM64 by building with the Dockerfile from the dev branch, or do I have to wait for 0.3.x?
@danielehrhardt commented on GitHub (Jan 19, 2025):
Some Updates here?
@eduardolat
@eduardolat commented on GitHub (Feb 6, 2025):
Guys, I'm pleased to inform you that this issue has been resolved as of v0.4.0 which you can start using now.
I've improved the way images are built and tested thanks to the new ARM runners on github actions.
I've also tested the resulting images myself on an ARM VPS with an Ampere processor.
I hope you like it.
@electric-m commented on GitHub (Feb 6, 2025):
Thank you so much, it is awesome!