search

realies / soulseek-docker

🐳 Soulseek Docker Container
https://hub.docker.com/r/realies/soulseek/
MIT License
210 stars 35 forks source link

No `vncpasswd` #45

Closed adriano-poci closed 2 years ago

adriano-poci commented 2 years ago

I have Docker set up on my Asustor NAS.

I had been using this container for quite some time, until the other day it stopped working.

I had set the VNCPWD environment variable, and it worked. Then the other day the container wasn't running and the log shows /init.sh: 14: vncpasswd: not found The container immediately stops after execution.

Curiously, if I remove the VNCPWD variable and re-launch the container, I get

2022-05-05 10:51:43,100 INFO Set uid to user 1000 succeeded
2022-05-05 10:51:43,104 INFO supervisord started with pid 22
2022-05-05 10:51:44,110 INFO spawned: 'tigervnc' with pid 23
2022-05-05 10:51:44,112 INFO spawned: 'openbox' with pid 24
2022-05-05 10:51:44,176 INFO spawned: 'novnc' with pid 25
2022-05-05 10:51:44,178 INFO spawned: 'soulseek' with pid 26
2022-05-05 10:51:44,463 INFO exited: soulseek (exit status 1; not expected)
2022-05-05 10:51:45,372 INFO success: tigervnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-05-05 10:51:45,372 INFO success: openbox entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-05-05 10:51:45,373 INFO success: novnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-05-05 10:51:45,763 INFO spawned: 'soulseek' with pid 42
2022-05-05 10:51:46,240 INFO exited: openbox (terminated by SIGABRT; not expected)
2022-05-05 10:51:46,251 INFO spawned: 'openbox' with pid 43
2022-05-05 10:51:47,294 INFO success: openbox entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-05-05 10:51:47,296 INFO success: soulseek entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-05-05 10:51:47,296 INFO exited: openbox (terminated by SIGABRT; not expected)
2022-05-05 10:51:48,299 INFO spawned: 'openbox' with pid 44
2022-05-05 10:51:49,342 INFO success: openbox entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-05-05 10:51:49,343 INFO exited: openbox (terminated by SIGABRT; not expected)
2022-05-05 10:51:50,346 INFO spawned: 'openbox' with pid 45
2022-05-05 10:51:51,389 INFO success: openbox entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-05-05 10:51:51,390 INFO exited: openbox (terminated by SIGABRT; not expected)
2022-05-05 10:51:52,393 INFO spawned: 'openbox' with pid 46
2022-05-05 10:51:53,446 INFO success: openbox entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-05-05 10:51:53,446 INFO exited: openbox (terminated by SIGABRT; not expected)
2022-05-05 10:51:54,448 INFO spawned: 'openbox' with pid 47
2022-05-05 10:51:55,493 INFO success: openbox entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-05-05 10:51:55,494 INFO exited: openbox (terminated by SIGABRT; not expected)
2022-05-05 10:51:56,497 INFO spawned: 'openbox' with pid 48
2022-05-05 10:51:57,540 INFO success: openbox entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-05-05 10:51:57,540 INFO exited: openbox (terminated by SIGABRT; not expected)
2022-05-05 10:51:58,544 INFO spawned: 'openbox' with pid 49
2022-05-05 10:51:59,588 INFO success: openbox entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-05-05 10:51:59,588 INFO exited: openbox (terminated by SIGABRT; not expected)
2022-05-05 10:52:00,591 INFO spawned: 'openbox' with pid 50
2022-05-05 10:52:01,635 INFO success: openbox entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-05-05 10:52:01,667 INFO exited: openbox (terminated by SIGABRT; not expected)
2022-05-05 10:52:02,670 INFO spawned: 'openbox' with pid 51
2022-05-05 10:52:03,722 INFO success: openbox entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-05-05 10:52:03,722 INFO exited: openbox (terminated by SIGABRT; not expected)
2022-05-05 10:52:04,726 INFO spawned: 'openbox' with pid 52
2022-05-05 10:52:04,777 INFO exited: openbox (terminated by SIGABRT; not expected)
2022-05-05 10:52:05,780 INFO spawned: 'openbox' with pid 53
2022-05-05 10:52:05,823 INFO exited: openbox (terminated by SIGABRT; not expected)
2022-05-05 10:52:07,828 INFO spawned: 'openbox' with pid 54
2022-05-05 10:52:08,871 INFO success: openbox entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-05-05 10:52:08,871 INFO exited: openbox (terminated by SIGABRT; not expected)
2022-05-05 10:52:09,874 INFO spawned: 'openbox' with pid 55
2022-05-05 10:52:10,917 INFO success: openbox entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-05-05 10:52:10,917 INFO exited: openbox (terminated by SIGABRT; not expected)
2022-05-05 10:52:11,920 INFO spawned: 'openbox' with pid 56
2022-05-05 10:52:13,035 INFO success: openbox entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-05-05 10:52:13,035 INFO exited: openbox (terminated by SIGABRT; not expected)
2022-05-05 10:52:14,038 INFO spawned: 'openbox' with pid 57
2022-05-05 10:52:15,082 INFO success: openbox entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-05-05 10:52:15,082 INFO exited: openbox (terminated by SIGABRT; not expected)
2022-05-05 10:52:16,085 INFO spawned: 'openbox' with pid 58
2022-05-05 10:52:16,133 INFO exited: openbox (terminated by SIGABRT; not expected)
2022-05-05 10:52:17,135 INFO spawned: 'openbox' with pid 59
2022-05-05 10:52:18,193 INFO success: openbox entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-05-05 10:52:18,193 INFO exited: openbox (terminated by SIGABRT; not expected)
2022-05-05 10:52:19,196 INFO spawned: 'openbox' with pid 60
2022-05-05 10:52:19,240 INFO exited: openbox (terminated by SIGABRT; not expected)
2022-05-05 10:52:20,243 INFO spawned: 'openbox' with pid 61
2022-05-05 10:52:20,286 INFO exited: openbox (terminated by SIGABRT; not expected)
2022-05-05 10:52:22,290 INFO spawned: 'openbox' with pid 62
2022-05-05 10:52:22,341 INFO exited: openbox (terminated by SIGABRT; not expected)
2022-05-05 10:52:25,347 INFO spawned: 'openbox' with pid 63
2022-05-05 10:52:25,838 INFO exited: openbox (terminated by SIGABRT; not expected)
2022-05-05 10:52:26,840 INFO gave up: openbox entered FATAL state, too many start retries too quickly

In this instance, I can open the webpage, and it shows noVNC connecting, but then the entire page goes black, including the cursor disappearing. However, in this case, the container stays running. I can exec into it, and indeed I can not locate the vncpasswd executable. But I also can not use the container because the VNC doesn't start up correctly.

This has been the case for the two most recent images, including the update just a few hours ago.

EDIT: The contents of /tmp/openbox-stderr---supervisor-...log:

(openbox:63): GLib-ERROR **: 10:52:25.837: file ../../../g
lib/gthread-posix.c: line 1339 (g_system_thread_new): erro
r 'Operation not permitted' during 'pthread_create'
How are you gentlemen? All your base are belong to us. (Op
enbox received signal 5)

many times repeated.

realies commented 2 years ago

Just force pulled the latest image and ran the container using the following command without any issues:

docker run -d --name='soulseek' -e 'PUID'='99' -e 'PGID'='100' -p '55012:55012/tcp' -v '/mnt/user/appdata/soulseek':'/data/.SoulseekQt':'rw' -v '/mnt/user/soulseek':'/data/Soulseek Downloads':'rw' 'realies/soulseek'

Does it work fine if you build the image locally using the Dockerfile? Or by pinning ubuntu to :focal instead of :latest here https://github.com/realies/soulseek-docker/blob/master/Dockerfile#L1?

rudluff commented 2 years ago

I had this problem too (although running it from the commandline worked, just docker compose was not behaving with VNCPWD) and changing ubuntu to :focal worked. Thanks realies.

realies commented 2 years ago

:latest should now work as expected, let me know if it still acts up

psociety commented 2 years ago

It now stopped working for me since last update :(

This is my config:

  soulseek:
    container_name: soulseek
    image: realies/soulseek
    restart: unless-stopped
    environment:
      - pgid=1000
      - puid=1000
      - resize=scale
      - resolution=1280x720
    ports:
      - 6080:6080
    volumes:
      - /storage/soulseek/config:/data/.SoulseekQt
      - /storage/soulseek/logs:/data/Soulseek Chat Logs
      - /storage/soulseek/downloads:/data/Soulseek Downloads
      - /storage/collection/music:/data/Soulseek Shared Folder

Docker log (same messages on loop):

2022-06-08 18:41:19,169 INFO success: openbox entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-06-08 18:41:19,169 INFO exited: openbox (terminated by SIGABRT (core dumped); not expected)
2022-06-08 18:41:20,173 INFO spawned: 'openbox' with pid 55

I've tried recreating the container and it didn't work.