s6-sudoc: fatal: unable to get exit status from server

[inctiveo]

I've been unable to get soulseek working since the user issue with PUID/PGID several months ago (issue #88). The resolution was to use PUID=0 and PGID=0 to run as root but this does not work for me.

To clarify the yaml file below, I've been running soulseek on gluetun (vpn container network) for the past year without issues on my Synology NAS. I've only included the relevant config for soulseek as it's part of a larger docker compose. Currently I am running as root as shown, previously it was my specified docker user.

YAML File

  soulseek:
    image: realies/soulseek:latest
    container_name: soulseek
    environment:
      - PUID=0
      - PGID=0
      - TZ=Europe/London
      - UMASK=022
    volumes:
      - /volume1/docker/soulseek/appdata:/data/.SoulseekQt
      - /volume1/docker/soulseek/logs:/data/Soulseek Chat Logs
      - /volume1/data/soulseek:/data/Soulseek Downloads
      - /volume1/data/media/music:/data/Soulseek Shared Folder
    network_mode: service:gluetun
    depends_on:
      gluetun:
        condition: service_healthy
    security_opt:
      - no-new-privileges:true
    restart: always

Container Logs

s6-rc: info: service svc-tigervnc: starting
s6-rc: info: service svc-soulseek: starting
s6-rc: info: service svc-openbox: starting
s6-rc: info: service svc-novnc: starting
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service svc-soulseek successfully started
s6-rc: info: service svc-tigervnc successfully started
s6-rc: info: service svc-novnc successfully started
s6-rc: info: service svc-openbox successfully started
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service init-setup: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
Warning: could not find self.pem
Using local websockify at /usr/share/novnc/utils/websockify/run
Starting webserver and WebSockets proxy on port 6080
Xvnc TigerVNC 1.13.1 - built 2024-04-01 08:26
Copyright (C) 1999-2022 TigerVNC Team and many others (see README.rst)
See https://www.tigervnc.org for information on TigerVNC.
Underlying X server release 12101011
Thu Jun 20 18:04:11 2024
 vncext:      VNC extension running!
 vncext:      Listening for VNC connections on all interface(s), port 5900
 vncext:      created VNC server for screen 0
s6-rc: fatal: timed out
s6-sudoc: fatal: unable to get exit status from server: Operation timed out
Navigate to this URL:
    http://72ad8c32905b:6080/vnc.html?host=72ad8c32905b&port=6080
Press Ctrl-C to exit
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Could not resolve keysym XF86CameraAccessEnable
> Warning:          Could not resolve keysym XF86CameraAccessDisable
> Warning:          Could not resolve keysym XF86CameraAccessToggle
> Warning:          Could not resolve keysym XF86NextElement
> Warning:          Could not resolve keysym XF86PreviousElement
> Warning:          Could not resolve keysym XF86AutopilotEngageToggle
> Warning:          Could not resolve keysym XF86MarkWaypoint
> Warning:          Could not resolve keysym XF86Sos
> Warning:          Could not resolve keysym XF86NavChart
> Warning:          Could not resolve keysym XF86FishingChart
> Warning:          Could not resolve keysym XF86SingleRangeRadar
> Warning:          Could not resolve keysym XF86DualRangeRadar
> Warning:          Could not resolve keysym XF86RadarOverlay
> Warning:          Could not resolve keysym XF86TraditionalSonar
> Warning:          Could not resolve keysym XF86ClearvuSonar
> Warning:          Could not resolve keysym XF86SidevuSonar
> Warning:          Could not resolve keysym XF86NavInfo
Errors from xkbcomp are not fatal to the X server
[mi] mieq: warning: overriding existing handler (nil) with 0x56210972f580 for event 2
[mi] mieq: warning: overriding existing handler (nil) with 0x56210972f580 for event 3
WebSocket server settings:
  - Listen on :6080
  - Web server. Web root: /usr/share/novnc
  - No SSL/TLS support (no cert file)
  - proxying from :6080 to localhost:5900

[realies]

does it work without the security options or vpn network?

[inctiveo]

Unfortunately not, I tested it on the default bridge network without the security option. Same output in the logs.

[realies]

what's the platform/os/docker version?

[inctiveo]

Synology DS1621+ running on DSM 7.2-64570 Update 3 and everything is done via container manager in DSM, which is running on the latest update.

[realies]

i don't own any synology hardware, what's under the hood?

[inctiveo]

CPU: 2.2GHz 4 Core AMD Ryzen V1500B (64-bit) RAM: 32GB DDR4 ECC SODIMM M.2 Drive Slots: 500GB Kingston NVMe PCIe Drive Bays: 4TB Seagate IronWolf

If you need anymore info let me know thanks

[realies]

output of uname -a and docker --version

[inctiveo]

uname -a

Linux DS1621PLUS 4.4.302+ #64570 SMP Thu Jul 20 00:06:39 CST 2023 x86_64 GNU/Linux synology_v1000_1621+

docker --version

Docker version 20.10.23, build 876964a

[inctiveo]

Resolved with recent soulseek update and running as docker user/group as normal.