-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Unable to run o Raspberry Pi 4 Model B Rev 1.5 (ARMv8) #107
Comments
@Joaav Are you still working on this issue? I could help to have a look. |
@Chapoly1305 I wasn't able to get it to work so far :( |
I am a docker noob, the only thing I can say is "Have you tried with podman" |
I didn't. I think issue is with rpi's CPU infrastructure. I will try to set this up in docker on Synology NAS |
I believe aarch64 is alright, x86, x86_64, armv7, armv8 shall work without problem. I just setup a brand new raspberry pi os, the docker image works fine on my env. The service is provided in http, not https, could you try Also, have you modified the docker daemon.json, or anything making the docker deviate from original state? If you can post the log of the container, would be quite helpful. |
Hi Thank you for all your help. I tried various curls. Ended up setting this up on my NAS without any issues whatsoever. What rPi are you on? Please see this thread: MatthewKuKanich/FindMyFlipper#41 Maybe it's an issue with 4B as the creator of FMF also couldn't get it to work. |
Basic info:
I am running command:
docker run -d --restart always --name anisette-v3 -p 6969:6969 dadoum/anisette-v3-server:latest
After that container is running and returns following with input
docker container ls
Unfortunately input
curl https://localhost:6969
returns:curl: (7) Failed to connect to localhost port 6969: Connection refused
or
curl: (56) Recv failure: Connection reset by peer
When running
docker container ls
again I get no information on portsdocker logs
command doesn't give me anythingdocker service logs
command gives me this:Error response from daemon: This node is not a swarm manager. Use "docker swarm init" or "docker swarm join" to connect this node to swarm and try again.
Any help would be appreciated as I am tearing my hair out and cannot get this to work
The text was updated successfully, but these errors were encountered: