Core (sigsegv) on startup with QNAP and 2.3 series about docker-unms HOT 4 OPEN

Hi, sorry for the late reply, do I understand correctly that docker logs docker-unms-1 returns nothing at all? Can you post the output if it does return something?

from docker-unms.

from docker-unms.

Hmm, possible. The only thing I can think of that will cause the whole container to crash would be if the s6-supervise process /init died.

In that case it would be good to know if it also happens when trying to run the base image (nico640/s6-alpine-node), because that would narrow it down quite a bit.

Something like this:

docker run -d --name s6-test-latest nico640/s6-alpine-node:latest

then check if the container crashes or stays running and if there is anything in the logs (there should only be a few lines because the image doesn't actually do anything)

If it does crash, I have pushed a new image on the testing tag with a updated version of s6-supervise, check if that one also crashes:

docker run -d --name s6-test-testing nico640/s6-alpine-node:testing

from docker-unms.

The s6-test-latest crashes, immediately. docker container logs s6-test-latest returns nothing at all. Same thing seems to happen with the s6-test-testing one. It downloads, starts, and then just stops with no apparent messages. I you try to start it again, it starts, then just stops - nothing is ever displayed and no logs.

from docker-unms.