-
Notifications
You must be signed in to change notification settings - Fork 9
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
Raspberry pi issues #200
Comments
You shouldn't need to use qemu, as all of the servers support ARM64. Have you installed a 64-bit operating system on the Pi? This won't work with a 32-bit operating system. |
It’s arm64 lite OS. Is there any way I could build the containers on a computer for arm64? |
It should work if you use qemu on the computer and copy the images over to the Pi. I haven't tested this, though. I assumed you meant using qemu on the Pi before. By the way, why can't you build the container images on the Pi? System requirements issue? |
I did mean on the pi, but I also tried qemu on the pc for building and it had an error in multiple of the repos, I’ll give you one as soon as possible. |
Are there precompiled images anywhere? |
There are pre-compiled images in the Pretendo server repos, but they don't include my pretendo-docker-specific patches. I guess you could manually fork the repos, apply the patches, and build the images with GitHub Actions, but then you'd have to manually update your repos on every update. |
How can I apply the patches? |
The patches are in the Although in my opinion, figuring out why the ARM64 builds aren't working would be a better solution. |
I just edited the test.yml workflow in my fork and made it export the containers in arm64. It built and outputted artifacts successfully and I'll let you know if it works. |
Had to use qemu to get the containers to run on my raspberry pi in the first place. Now the connections always refuse to everything. Even the url of the proxy itself. There’s also mongodb not working in the logs and refusing connection.
The text was updated successfully, but these errors were encountered: