Open SiNaPsEr0x opened 1 year ago
Hey there, thanks for opening this issue and for using this software! May I ask you some more details about the environment (e.g. Docker version, OS) and what is the command / docker-compose file you are using to spin this up?
I have qnap with armv7 procs alpine
Could you please tell me what is the digest of the specific desktainer Docker image you are using?
And please could you provide the content of the Xvfb log (you can find it in /var/log/supervisor
inside the container)
Thanks :)
there is 2 log.. this is your..
root@7ad041b0046c:/var/log/supervisor# cat Xvfb-stderr---supervisor-dxtjkcth.log
(EE)
(EE) Backtrace:
(EE)
(EE) Segmentation fault at address 0x6c69615e
(EE)
Fatal server error:
(EE) Caught signal 11 (Segmentation fault). Server aborting
(EE)
(EE)
(EE) Backtrace:
(EE)
(EE) Segmentation fault at address 0x6c69615e
(EE)
Fatal server error:
(EE) Caught signal 11 (Segmentation fault). Server aborting
(EE)
(EE)
(EE) Backtrace:
(EE)
(EE) Segmentation fault at address 0x6c69615e
(EE)
Fatal server error:
(EE) Caught signal 11 (Segmentation fault). Server aborting
(EE)
(EE)
(EE) Backtrace:
(EE)
(EE) Segmentation fault at address 0x6c69615e
(EE)
Fatal server error:
(EE) Caught signal 11 (Segmentation fault). Server aborting
(EE)
root@7ad041b0046c:/var/log/supervisor#
and this st error from console:
Enabling custom user: mainuser
Creating custom user mainuser
Setting custom user's password
VNC port set to 5901
noVNC port set to 6901
Resolution set to 1920x1080
VNC password disabled
Starting supervisord
2023-04-17 15:27:47,647 WARN No file matches via include "/etc/supervisor/conf.d/*.conf"
2023-04-17 15:27:47,648 INFO Set uid to user 0 succeeded
2023-04-17 15:27:47,657 INFO supervisord started with pid 1
2023-04-17 15:27:48,661 INFO spawned: 'Xvfb' with pid 24
2023-04-17 15:27:48,665 INFO spawned: 'LXDE' with pid 25
2023-04-17 15:27:48,670 INFO spawned: 'x11vnc' with pid 26
2023-04-17 15:27:48,674 INFO spawned: 'noVNC' with pid 27
2023-04-17 15:27:48,740 INFO exited: x11vnc (exit status 1; not expected)
2023-04-17 15:27:48,762 INFO exited: Xvfb (terminated by SIGABRT; not expected)
2023-04-17 15:27:48,989 INFO reaped unknown pid 38 (exit status 0)
2023-04-17 15:27:48,994 INFO exited: LXDE (exit status 1; not expected)
2023-04-17 15:27:50,155 INFO spawned: 'Xvfb' with pid 39
2023-04-17 15:27:50,158 INFO spawned: 'LXDE' with pid 40
2023-04-17 15:27:50,164 INFO spawned: 'x11vnc' with pid 41
2023-04-17 15:27:50,169 INFO success: noVNC entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-04-17 15:27:50,195 INFO exited: Xvfb (terminated by SIGABRT; not expected)
2023-04-17 15:27:50,198 INFO exited: x11vnc (exit status 1; not expected)
2023-04-17 15:27:50,229 INFO reaped unknown pid 50 (exit status 0)
2023-04-17 15:27:51,237 INFO success: LXDE entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-04-17 15:27:51,237 INFO exited: LXDE (exit status 1; not expected)
2023-04-17 15:27:52,241 INFO spawned: 'Xvfb' with pid 51
2023-04-17 15:27:52,248 INFO spawned: 'LXDE' with pid 52
2023-04-17 15:27:52,252 INFO spawned: 'x11vnc' with pid 53
2023-04-17 15:27:52,254 INFO reaped unknown pid 37 (exit status 1)
2023-04-17 15:27:52,276 INFO exited: Xvfb (terminated by SIGABRT; not expected)
2023-04-17 15:27:52,293 INFO exited: x11vnc (exit status 1; not expected)
2023-04-17 15:27:52,320 INFO reaped unknown pid 62 (exit status 0)
2023-04-17 15:27:52,326 INFO exited: LXDE (exit status 1; not expected)
2023-04-17 15:27:53,330 INFO spawned: 'LXDE' with pid 63
2023-04-17 15:27:53,331 INFO reaped unknown pid 49 (exit status 1)
2023-04-17 15:27:53,382 INFO reaped unknown pid 72 (exit status 0)
2023-04-17 15:27:54,390 INFO success: LXDE entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-04-17 15:27:54,390 INFO exited: LXDE (exit status 1; not expected)
2023-04-17 15:27:55,394 INFO spawned: 'Xvfb' with pid 73
2023-04-17 15:27:55,398 INFO spawned: 'LXDE' with pid 74
2023-04-17 15:27:55,404 INFO spawned: 'x11vnc' with pid 75
2023-04-17 15:27:55,405 INFO reaped unknown pid 61 (exit status 1)
2023-04-17 15:27:55,420 INFO exited: Xvfb (terminated by SIGABRT; not expected)
2023-04-17 15:27:55,435 INFO gave up: Xvfb entered FATAL state, too many start retries too quickly
2023-04-17 15:27:55,462 INFO exited: x11vnc (exit status 1; not expected)
2023-04-17 15:27:55,462 INFO reaped unknown pid 84 (terminated by SIGTERM)
2023-04-17 15:27:55,468 INFO gave up: x11vnc entered FATAL state, too many start retries too quickly
2023-04-17 15:27:55,470 INFO exited: LXDE (exit status 1; not expected)
2023-04-17 15:27:56,473 INFO spawned: 'LXDE' with pid 85
2023-04-17 15:27:56,474 INFO reaped unknown pid 71 (exit status 1)
2023-04-17 15:27:56,524 INFO reaped unknown pid 94 (exit status 0)
2023-04-17 15:27:56,530 INFO exited: LXDE (exit status 1; not expected)
2023-04-17 15:27:58,535 INFO spawned: 'LXDE' with pid 95
2023-04-17 15:27:58,536 INFO reaped unknown pid 83 (exit status 1)
2023-04-17 15:27:58,587 INFO reaped unknown pid 104 (exit status 0)
2023-04-17 15:27:58,593 INFO exited: LXDE (exit status 1; not expected)
2023-04-17 15:27:59,595 INFO reaped unknown pid 93 (exit status 1)
2023-04-17 15:28:01,599 INFO spawned: 'LXDE' with pid 105
2023-04-17 15:28:01,600 INFO reaped unknown pid 103 (exit status 1)
2023-04-17 15:28:01,650 INFO reaped unknown pid 114 (exit status 0)
2023-04-17 15:28:01,656 INFO exited: LXDE (exit status 1; not expected)
2023-04-17 15:28:02,658 INFO gave up: LXDE entered FATAL state, too many start retries too quickly
2023-04-17 15:28:04,660 INFO reaped unknown pid 113 (exit status 1)
Hey there @SiNaPsEr0x, thanks for sharing your log. Based on your answers, I assume that you're running the dmotte/desktainer:2023.04.13.2110
image on arm/v7
architecture.
Unfortunately, the log is not very useful because it just tells us that there has been a segmentation fault while trying to start Xvfb.
I don't have a qnap, so I tried to run the image on this setup:
apt install docker.io
)docker run -it --rm -p 6901:6901 dmotte/desktainer
In my case everything works fine.
The problem you are facing is pretty strange and requires further investigation, but I'm unable to replicate your issue, so I'm afraid I cannot help :(
Have you tried it on a "normal" host (not qnap)? Does it work in that case? Maybe this could be kernel-related or maybe qnap just doesn't provide full Docker support, who knows
Yes the problem is only on qnap ts231P2... if you can do some tests on armhf you would make many of us qnap owners happy
Docker on qnap is Limited but ubuntunovnc run correctly with supervisor
Hey @SiNaPsEr0x, I updated both the desktainer
and desktainer-rootless
images to Debian 12 "bookworm". This means that Xvfb has been upgraded from version 2:1.20.11-1+deb11u6
to 2:21.1.7-3
. Maybe something could have changed regarding qnap support. Would you please try again? Thanks a lot
Yes the problem is only on qnap ts231P2... if you can do some tests on armhf you would make many of us qnap owners happy
Docker on qnap is Limited but ubuntunovnc run correctly with supervisor
Some QNAPs with armv7 was updated with page size 32K after that some containers that was created for page size 4K didnt work.
this is log: