-
-
Notifications
You must be signed in to change notification settings - Fork 534
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
nitter docker arm64 tested on RPI4 #399
Comments
Update 26/03/2023, please use the official ARM64 docker image: I have published a Docker image that is compatible with ARM64, intel x86/AMD64 and maybe with ARMv7 (not tested): https://quay.io/repository/unixfox/nitter The image is based on https://github.com/goodtiding5/docker-nitter, so it is a bit different from the original nitter docker image. The source code is here: https://github.com/unixfox/periodic-build-with-github-actions/tree/master/nitter |
Thank you @unixfox! I've added a link to the readme so people won't trip over the broken ARM64 image in the official Docker repo. |
ح |
Actually looking at Could we re-open this issue to allow tracking in the future? |
How do you want to build a docker image for another platform other than |
My comment was somewhat out of place - in the next sentence I already mentioned: "I guess it boils down to lack of nim's base image for arm64" so I'm aware of it. I wonder what's the main roadblock for nimlang to provide multi-arch images, considering that there are unofficial ones that (seems to) work, like the one that you use (ghcr.io/maxisoft/nim-docker-images/nim) |
Please use new the official ARM64 docker image: |
As i couldn't build docker version for arm64 as the nim-alpine docker only available for amd64 due dockerhub does not build for arm on its own. There are other solutions ,but until then i recreated the Dockerfile with the original nim building docker.
If someone willing to experiment with it. Tested on RPI4 ,build time around 1 hour.
New Dockerfile for arm64
The text was updated successfully, but these errors were encountered: