Dadoum / Provision

Set of tools interracting with Apple servers. Don't hesitate to leave a star if you appreciate it.
496 stars 3.2k forks source link

Unable to run o Raspberry Pi 4 Model B Rev 1.5 (ARMv8) #107

Open Joaav opened 4 months ago

Joaav commented 4 months ago

Basic info:

Operating System: Raspbian GNU/Linux 11 (bullseye)
Kernel: Linux 6.1.21-v8+
Architecture: arm64
processor   : 0
BogoMIPS    : 108.00
Features    : fp asimd evtstrm crc32 cpuid
CPU implementer : 0x41
CPU architecture: 8
CPU variant : 0x0
CPU part    : 0xd08
CPU revision    : 3

processor   : 1
BogoMIPS    : 108.00
Features    : fp asimd evtstrm crc32 cpuid
CPU implementer : 0x41
CPU architecture: 8
CPU variant : 0x0
CPU part    : 0xd08
CPU revision    : 3

processor   : 2
BogoMIPS    : 108.00
Features    : fp asimd evtstrm crc32 cpuid
CPU implementer : 0x41
CPU architecture: 8
CPU variant : 0x0
CPU part    : 0xd08
CPU revision    : 3

processor   : 3
BogoMIPS    : 108.00
Features    : fp asimd evtstrm crc32 cpuid
CPU implementer : 0x41
CPU architecture: 8
CPU variant : 0x0
CPU part    : 0xd08
CPU revision    : 3

Hardware    : BCM2835
Revision    : b03115
Serial      : 10000000e7d160c0
Model       : Raspberry Pi 4 Model B Rev 1.5

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

CONTAINER ID   IMAGE                              COMMAND                  CREATED          STATUS         PORTS                                       NAMES
8ed8f6f8f810   dadoum/anisette-v3-server:latest   "/opt/anisette-v3-se…"   58 seconds ago   Up 2 seconds   0.0.0.0:6969->6969/tcp, :::6969->6969/tcp   anisette-v3

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 ports

CONTAINER ID   IMAGE                              COMMAND                  CREATED          STATUS                            PORTS     NAMES
8ed8f6f8f810   dadoum/anisette-v3-server:latest   "/opt/anisette-v3-se…"   10 minutes ago   Restarting (139) 36 seconds ago             anisette-v3

docker logs command doesn't give me anything

docker 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

Chapoly1305 commented 1 month ago

@Joaav Are you still working on this issue? I could help to have a look.

Joaav commented 1 month ago

@Chapoly1305 I wasn't able to get it to work so far :(

Dadoum commented 1 month ago

I am a docker noob, the only thing I can say is "Have you tried with podman"

Joaav commented 1 month ago

I didn't. I think issue is with rpi's CPU infrastructure. I will try to set this up in docker on Synology NAS

Chapoly1305 commented 1 month ago

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 curl http://localhost:6969 again?

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. docker logs -f 8ed8f6f8f810. The 8ed8f6f8f810 is the container ID, you can find it with docker ps. I copied from your original post, you can update to the latest value if it somehow changed.

Joaav commented 1 month ago

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:

https://github.com/MatthewKuKanich/FindMyFlipper/issues/41

Maybe it's an issue with 4B as the creator of FMF also couldn't get it to work.