-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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) #19
Comments
Hi, any ideas how to fix this? |
I have the same issue. Anyone found a solution? |
I compiled from scratch using dub and executed without docker. Executing the build gives a Segmentation fault Error.
|
I ended up running it on my Synology NAS and it works there. No idea how to make it work on rpi. |
When using gdb to inspect a debug build I can trace the following errors:
|
@Joaav - Can you share screenshots of the settings/config you used to make it work on your Synology? I am having non-stop rebooting/crashing issues on when attempting to run on mine. |
Here are my steps:
I was using this to run find my flipper which required few additional steps - idk if you are interested in those. |
Take a look at this. I had the same issues. Resolved it here: |
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: