-
-
Notifications
You must be signed in to change notification settings - Fork 281
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ARM support #7
Comments
Hi, for this container to support ARM, 2 things are needed::
For 1), this is possible and I'm already working on adding support for multiple architectures. For 2), Firefox is currently not available for ARM on Alpine Linux, which means that Firefox needs to compiled manually. So for sure there will be some work to do on this side. |
Any ETA for ARM support for the baseimage? |
Since I work on this during my free time, it’s hard to give an ETA. However, I can say that more than 90% of the work is done. |
No rush, was just wondering how far it is.
Good to hear, looking forward to it. |
+1 for the ARM support; just upping as this the last comment if from over an year ago. |
+1. It looks like there is a Firefox package for Alpine... |
I'm trying to build my own baseimage, baseimage-gui and firefox image for my RPi4. Everything builds fine (a couple of small tweaks required, eg I had to use Firefox 75 as that's the only package available) and the firefox container boots and I can view Firefox in the browser for a second or so before I get the error below and the container shuts down. I have just built the filezilla image and it's working fine (apart from some strange artefacts as shown below) so the issue seems to be Firefox specific. Update |
+1 for ARM image. Will be grateful a lot! |
+1 |
@mtis88 If you managed to compile an image for RPi4, that would much anticipated. |
Though I'm not mtis88... :)
I will report my progress here and maybe I'll start a fork... |
Update:
Next steps are: clone docker-firefox repo, understand the build process, mange it into the above image, then build and run. |
Another update: I managed to build the image and launch jd2 (not FF yet). An update of jd2 (something which should be done in 5 minutes tops) took more than 90 minutes on my Raspi4, so I am now trying a different approach, will see whether I get better performance and revisit this if the performance issue turns out to be caused by jd2/java. |
Great stuff, looking forward to your updates! |
After exploring that other solution, I returned to this base profile, the performance issue seems to be affecting more the update process (which can be executed during image creation to a major extent). Still trying to make firefox work, right now it errors out. Permission/directory issue, will maybe investigate tomorrow. |
FF turned out to be super-slow on my pi4, so I went for falkon for now. Performance is stil meh, but better. |
Hello, is it still a possibility that this can get Raspberry Pi 32-bit (armhf) support? A similar Docker container for Firefox (ich777/firefox) was able to pull it off and I was just curious if it could be applied here in the same fashion. |
Is there any update on this to run on a 64-bit Raspberry Pi? |
I created a version that works on ARM. It's not super fast on a Pi4, but it's usable. |
Latest image is now multi-arch. |
Hello! Thanks for your container, it's neat!
I would like to run it on openmediavault. It worked properly on an x86 VM, but if I try it on my ARM (armhf) single-board computer, the container crashes with the following error:
standard_init_linux.go:190: exec user process caused "exec format error"
which, if I understand well, is due to an architecture mismatch. Are you positive your container indeed can't run on ARM? If so, would it take you a lot of work to change dependencies?
The text was updated successfully, but these errors were encountered: