Repository navigation
[BUG] wechat process does not start on Synology #4
Description
Is there an existing issue for this?
- I have searched the existing issues
Current Behavior
When running on a Synology NAS (SA6400, Kernel 5.10) the wechat process cannot be started.
Doesn't matter if I add seccomp command.
Expected Behavior
Wechat process can be started.
Steps To Reproduce
Run docker run or compose on Synology NAS.
Environment
- OS: DSM 7.2.2
- How docker service was installed: System app storeCPU architecture
x86-64
Docker creation
docker run -d \
--restart unless-stopped \
--name wechat_w \
--hostname wechat_w \
--shm-size="2g" \
--device /dev/dri:/dev/dri \
-e DRINODE=/dev/dri/renderD128 \
-e PUID=0 \
-e PGID=0 \
-e TZ=*** \
-e SUBFOLDER=/wechat_w/ \
-e TITLE=Wechat \
-e NO_DECOR=true \
-e SELKIES_SCALING_DPI=120 \
-p 3000:3000 \
-v /opt/docker/volume/wechat/config_w:/config \
ghcr.io/linuxserver/weixin:latestContainer logs
[migrations] started
[migrations] no migrations found
usermod: user abc is currently used by process 1
───────────────────────────────────────
██╗ ███████╗██╗ ██████╗
██║ ██╔════╝██║██╔═══██╗
██║ ███████╗██║██║ ██║
██║ ╚════██║██║██║ ██║
███████╗███████║██║╚██████╔╝
╚══════╝╚══════╝╚═╝ ╚═════╝
Brought to you by linuxserver.io
───────────────────────────────────────
To support LSIO projects visit:
https://www.linuxserver.io/donate/
───────────────────────────────────────
GID/UID
───────────────────────────────────────
User UID: 0
User GID: 0
───────────────────────────────────────
..+.+............+........+....+..+....+.....+......+++++++++++++++++++++++++++++++++++++++*.......+++++++++++++++++++++++++++++++++++++++*...+........+.......+..+.+...............+.........+........+......+.+...+......+..+.......+.....................++++++
....+......+...+...+..+.......+......+........+.+..............+......+...+++++++++++++++++++++++++++++++++++++++*.+......+++++++++++++++++++++++++++++++++++++++*....+....+.....+...+...+................+.....+...+......+.+...+..+......+..........+...+..............+...............+...............+.+......+.........+......+.....+......+.........+...+......+....+...+...+...........+.............+..+...+...+...+....+......+.....+....+...+.........+......+.........+...+........+...+.+.....................+....................+..........+..+............+.+...+.....+......+......+............+.....................+......+....+....................+.+......+........+....+..+.+..+.+......+..............+...............+.......+............+...+.....+...................+...+......+.....+.+.....+.........+.+........+.+..+...+....+..................+............+......+....................+.......++++++
-----
[ls.io-init] Creating initial backup of menu.xml
[ls.io-init] Creating initial backup of system rc.xml
[ls.io-init] Removing window decorations
[ls.io-init] Disabling maximization
**** permissions for /dev/dri/renderD128 are good ****
**** permissions for /dev/dri/card0 are good ****
[custom-init] No custom files found, skipping...
xsettingsd: Loaded 1 setting from /config/.xsettingsd
screen 0 shmid 0
Connection failure: Connection refused
pa_context_connect() failed: Connection refused
[ls.io-init] done.
WARNING: Kernel has no file descriptor comparison support: Function not implemented
xsettingsd: Created window 0x200001 on screen 0 with timestamp 4156331924
xsettingsd: Selection _XSETTINGS_S0 is owned by 0x0
xsettingsd: Took ownership of selection _XSETTINGS_S0
17
INFO:selkies.__main__:Starting mode 'websockets'...
INFO:selkies.__main__:Starting Selkies in 'websockets' mode.
INFO:data_websocket:pcmflux library found. Audio capture is available.
INFO:data_websocket:pixelflux library found. Striped encoding modes available.
Activity
LinuxServer-CI commentedon Mar 5, 2026
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.
thelamer commentedon Apr 4, 2026
Synology ships a stripped kernel, old Docker, and never upgrades it. As time goes on more and more applications will continue to be incompatible with it.
This is a modern electron application running on a head distro, there is nothing I can do in the container to fix this.
I would keep this in mind the next time you make a NAS purchase they are notorious at this point for this specific issue, they hide behind "security and reliability" but my bet is upgrading the operating system and kernel X% of units do not come back online so they only do it when absolutely necessary or require you buy a new device to get the latest updates.
christaikobo commentedon Apr 5, 2026
OK thanks for the information.