Node stopped working as docker container on qnap-container-station

Node Operators troubleshooting
,
42 
[/var/log/container-station] # docker run -d --restart unless-stopped \
>     -p xx:28967:28967/tcp \
>     -p xx:28967:28967/udp \
>     -p xx:14002:14002 \
>     -e WALLET="xx" \
>     -e EMAIL="xx" \
>     -e ADDRESS="xx:28967" \
>     -e STORAGE="25TB" \
>     -m 6144M \
>     --user $(id -u):$(id -g) \
>     --mount type=bind,source="/share/Container/STORJ/identity",destination=/app/identity \
>     --mount type=bind,source="/share/Container/STORJ/config",destination=/app/config \
>     --stop-timeout 300 \
>     --platform "linux/arm/v5" \
>     --name storagenode storjlabs/storagenode:9109fd2
dcc1b753979d0719ab32aa83e822ef4814a82396f69bb09c13fd714c5aae4de9
[/var/log/container-station] #
[/var/log/container-station] # docker logs storagenode --follow
[/var/log/container-station] #

Screaming silence in docker logs

43

I cannot understand why. It must print something, at least that it doesn’t like an entrypoint

Could you please try to run it like this:

docker run -it --rm \
     -p xx:28967:28967/tcp \
     -p xx:28967:28967/udp \
     -p xx:14002:14002 \
     -e WALLET="xx" \
     -e EMAIL="xx" \
     -e ADDRESS="xx:28967" \
     -e STORAGE="25TB" \
     -m 6144M \
     --user $(id -u):$(id -g) \
     --mount type=bind,source="/share/Container/STORJ/identity",destination=/app/identity \
     --mount type=bind,source="/share/Container/STORJ/config",destination=/app/config \
     --stop-timeout 300 \
     --entrypoint bash \
     --name storagenode storjlabs/storagenode:9109fd2 --log.output=stdout

It should give you a prompt, then try to run an entrypoint script there:

bash -uexo pipefail /entrypoint

and post a result.

44

The command/container runs for a second - no bash, no output
I also removed the --log.output=stdout as it is piped to the bash inside the container - but - in 0c21bd6…

45

Oh, you are correct, this option should go to storagenode.
Could you please try to add bash instead of this option?

And that silence is do bother me. Does it do the same for debian:bookworm-slim image?

46

0c21bd6
Working - got bash in container
9109fd2
no output
debian:bookworm-slim
no output

47

Ok, so this is confirming my suspicions, the problem is in a newest Debian under this ARM32 CPU.
Now we need to figure out why is it happening.
Could you please share your model number? Perhaps there are discussions in the Internet about this.

Could you please also try to run the ubuntu:latest image?

48

woow…
Happy to locate the cockroach…

ubuntu isnt working too

we talk about QNAP TS-431X2

1 Like
49

Thank you for confirmation. I would share with the team, but seems it’s an issue with the Container Station on this model of QNAP and the mitigation is to run an outdated image for now.
It would auto update storagenode and storagenode-updater though, but the base OS is out of support.

50

32-bit ARMs are messy, there were tons of varietes with different subsets of supported instructions. Do you get anything in kernel logs when this happens? IIRC kernel reports binaries that either do not match the architecture, or use unsupported CPU instructions.