[BUG] Conflict with Synology Docker Version (20.10.3) #358

drewwats · 2023-04-17T14:31:36Z

Is there an existing issue for this?

I have searched the existing issues

Current Behavior

I believe this update introduced a breaking change for anyone running most recent version of Docker available via Synology Package Center. This same error now appears for many other linuxserver images. My experience with the linuxserver images, as of this morning, is summarized below.

BROKEN      ghcr.io/linuxserver/plex:latest
WORKING   ghcr.io/linuxserver/plex:1.31.3    
BROKEN      ghcr.io/linuxserver/sonarr:latest
WORKING    ghcr.io/linuxserver/sonarr:develop-4.0.0.448-ls448
BROKEN      ghcr.io/linuxserver/radarr:latest 
WORKING    ghcr.io/linuxserver/radarr:nightly-4.5.0.7075-ls460
BROKEN       ghcr.io/linuxserver/jackett:latest    
WORKING    ghcr.io/linuxserver/jackett:development-v0.20.3920-ls726
WORKING    ghcr.io/linuxserver/bazarr:latest        
WORKING    lscr.io/linuxserver/prowlarr:develop

Containers shows running, not restarting, but they are not functional.

For now, I am hardcoding previous versions (1.31.3 for Plex) or develop/nightly versions and it is working again, as expected.

I understand that this issue could be due to Synology using outdated Docker image, but the Synology community at least needs to be aware that many updated linuxserver images will cease to work.

Expected Behavior

Images should work as they did on previous versions.

Steps To Reproduce

On Synology devices running Docker Daemon 20.10.3
Run ghcr.io/linuxserver/plex:latest as shown in docker-compose below

Environment

- OS: DSM 7.1.1-42962 Update 4
- How docker service was installed: Synology Package Center

CPU architecture

x86-64

Docker creation

plex:
    image: ghcr.io/linuxserver/plex:latest
    container_name: plex
    network_mode: host
    cap_add:
      - SYS_NICE
    environment:
      - APP_NICENESS=-5
      - PUID=0
      - PGID=0
      - VERSION=latest
      - TZ=${TIME_ZONE}
      - ADVERTISE_IP=http://${LOCAL_IP}:32400/
    devices:
      - /dev/dri:/dev/dri
    volumes:
      - ${PLEX_HOME}:/config:rw
      - ${TV_DIR}:/tv:rw
      - ${MOVIE_DIR}:/movies:rw
    restart: unless-stopped

Container logs

PLEX
s6-rc-compile: fatal: invalid /etc/s6-overlay/s6-rc.d/init-plex-chown/type: must be oneshot, longrun, or bundle
s6-rc: fatal: unable to take locks: No such file or directory
s6-linux-init-shutdownd: warning: /run/s6/basedir/scripts/rc.shutdown exited 111
s6-rc-compile: fatal: invalid /etc/s6-overlay/s6-rc.d/init-plex-chown/type: must be oneshot, longrun, or bundle
SONARR
s6-rc-compile: fatal: invalid /etc/s6-overlay/s6-rc.d/init-sonarr-config/type: must be oneshot, longrun, or bundle
s6-rc: fatal: unable to take locks: No such file or directory
s6-linux-init-shutdownd: warning: /run/s6/basedir/scripts/rc.shutdown exited 111
s6-rc-compile: fatal: invalid /etc/s6-overlay/s6-rc.d/init-sonarr-config/type: must be oneshot, longrun, or bundle

The text was updated successfully, but these errors were encountered:

github-actions · 2023-04-17T14:32:13Z

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

thespad · 2023-04-17T14:40:46Z

I can't replicate this:

$ uname -a
Linux NAS2 4.4.180+ #42962 SMP Tue Jan 31 23:19:16 CST 2023 x86_64 GNU/Linux synology_apollolake_918+

$ docker run -d --rm --name=sonarr --tmpfs /config ghcr.io/linuxserver/sonarr:latest && docker logs -f sonarr
347f66c106b56271f2ea633c2623e18543ffabc4051054277579c886d65cdd1d
[migrations] started
[migrations] no migrations found
usermod: no changes
───────────────────────────────────────

      ██╗     ███████╗██╗ ██████╗
      ██║     ███████╗██║██║   ██║
      ██║     ╚════██║██║██║   ██║
      ███████╗███████║██║╚██████╔╝

   Brought to you by linuxserver.io
───────────────────────────────────────

To support the app dev(s) visit:
Sonarr: https://sonarr.tv/donate

To support LSIO projects visit:
https://www.linuxserver.io/donate/

User UID:    911
User GID:    911
───────────────────────────────────────

[custom-init] No custom files found, skipping...
[Info] Bootstrap: Starting Sonarr - /app/sonarr/bin/Sonarr.exe - Version 3.0.10.1567
[Info] AppFolderInfo: Data directory is being overridden to [/config]
[Info] Router: Application mode: Interactive
[Info] MigrationLogger: *** Checking database for required migrations data source=/config/sonarr.db;cache size=-10000;datetimekind=Utc;journal mode=Wal;pooling=True;version=3 ***

Though it's worth noting that we do not and never had supported running our containers with a root PUID/PGID.

drewwats · 2023-04-17T14:53:28Z

@thespad , thanks for verifying so quickly.

Just tried running ghcr.io/linuxserver/plex:latest with UID/GID removed and the error remains.

I updated the issue with additional images that are working using the same docker-compose file. There's something here, I'm just not sure what it is yet. Possibly worth note, we are running same version of DSM on different hardware.

$ uname -a
Linux Synology 4.4.180+ #42962 SMP Tue Jan 31 23:18:09 CST 2023 x86_64 GNU/Linux synology_geminilake_920+

aptalca · 2023-04-17T14:58:28Z

Remove APP_NICENESS?

drewwats · 2023-04-17T15:00:46Z

Remove APP_NICENESS?

Nope, same error.

thespad · 2023-04-17T15:02:50Z

So the only change between 1.31.3.6868-28fc46b27-ls1601 and 1.32.0.6918-6f393eda1-ls161 is the Plex package version, there aren't even any OS package updates. 1.32.0.6918-6f393eda1-ls162 (current latest) has a handful of OS package updates but nothing that is likely to cause any issue: 1.32.0.6918-6f393eda1-ls161...1.32.0.6918-6f393eda1-ls162.

I can't replicate the issue with any of the images you've listed. I've even tested on my old DS916+ and it's happy too:

$ uname -a
Linux NAS1 3.10.108 #42962 SMP Tue Oct 18 15:05:36 CST 2022 x86_64 GNU/Linux synology_braswell_916+

$ docker run -d --rm --name=test --tmpfs /config ghcr.io/linuxserver/plex:latest && docker logs -f test
101ac7224aec6286663e934325a8ee01898809f1c037e5b9d86116a039354a20
[migrations] started
[migrations] no migrations found
usermod: no changes
───────────────────────────────────────

      ██╗     ███████╗██╗ ██████╗
      ██║     ██╔════╝██║██╔═══██╗
      ██║     ███████╗██║██║   ██║
      ██║     ╚════██║██║██║   ██║
      ███████╗███████║██║╚██████╔╝
      ╚══════╝╚══════╝╚═╝ ╚═════╝

   Brought to you by linuxserver.io

User UID:    911
**** Server is unclaimed, but no claim token has been set ****



#######################################################
# Update routine will not run because you havent set  #
# the VERSION variable or you opted out of updates.   #
#          For more information checkout :-           #
#    https://github.com/linuxserver/docker-plex       #
#######################################################


[custom-init] No custom files found, skipping...
Starting Plex Media Server. . . (you can ignore the libusb_init error)

drewwats · 2023-04-17T15:07:45Z

So strange. I mean, even the release notes mention an update to s6v3, which seems to be referenced in the errors in the containers' logs.

LinuxServer Changes:

Rebase to jammy. Update to s6v3. Remove opencl packages (bundled with plex).

thespad · 2023-04-17T15:08:57Z

That update is from 16.10.22: - Rebase to jammy. Update to s6v3. Remove opencl packages (bundled with plex).

It's just a quirk of our release process that if nothing has changed in terms of our update notes, it duplicates the previous update.

aptalca · 2023-04-17T15:09:20Z

That was a while back and your working images are also on s6v3

Can you run the same command as thespad so we can compare apples to apples?

drewwats · 2023-04-17T15:12:04Z

Sure:

$ docker run -d --rm --name=test --tmpfs /config ghcr.io/linuxserver/plex:latest && docker logs -f test
697d35f8c50c8a2eb73809aae40d541e39d6d6a83007c362ee3439112d9baaa9
s6-rc-compile: fatal: invalid /etc/s6-overlay/s6-rc.d/init-plex-chown/type: must be oneshot, longrun, or bundle

j0nnymoe · 2023-04-17T15:13:36Z

What version is your kernel?

drewwats · 2023-04-17T15:16:45Z

What version is your kernel?

Linux Synology 4.4.180+ #42962 SMP Tue Jan 31 23:18:09 CST 2023 x86_64 GNU/Linux synology_geminilake_920+

aptalca · 2023-04-17T15:18:50Z

Can you try adding --security-opt seccomp=unconfined to the docker run above?
docker run -d --rm --name=test --security-opt seccomp=unconfined --tmpfs /config ghcr.io/linuxserver/plex:latest && docker logs -f test

j0nnymoe · 2023-04-17T15:20:31Z

Just tested on my DS1019+

j0nnymoe@nas01-syno:/$ sudo docker logs -f test
[migrations] started
[migrations] no migrations found
usermod: no changes
───────────────────────────────────────

      ██╗     ███████╗██╗ ██████╗
      ██║     ██╔════╝██║██╔═══██╗
      ██║     ███████╗██║██║   ██║
      ██║     ╚════██║██║██║   ██║
      ███████╗███████║██║╚██████╔╝
      ╚══════╝╚══════╝╚═╝ ╚═════╝

   Brought to you by linuxserver.io
───────────────────────────────────────

To support LSIO projects visit:
https://www.linuxserver.io/donate/

───────────────────────────────────────
GID/UID
───────────────────────────────────────

User UID:    911
User GID:    911
───────────────────────────────────────

**** Server is unclaimed, but no claim token has been set ****



#######################################################
# Update routine will not run because you havent set  #
# the VERSION variable or you opted out of updates.   #
#          For more information checkout :-           #
#    https://github.com/linuxserver/docker-plex       #
#######################################################


[custom-init] No custom files found, skipping...
Starting Plex Media Server. . . (you can ignore the libusb_init error)
[ls.io-init] done.

Linux nas01-syno 4.4.180+ #42661 SMP Mon Jun 27 15:05:48 CST 2022 x86_64 GNU/Linux synology_apollolake_1019+

drewwats · 2023-04-17T15:22:32Z

Can you try adding --security-opt seccomp=unconfined to the docker run above? docker run -d --rm --name=test --security-opt seccomp=unconfined --tmpfs /config ghcr.io/linuxserver/plex:latest && docker logs -f test

Same again :|

docker run -d --rm --name=test --security-opt seccomp=unconfined --tmpfs /config ghcr.io/linuxserver/plex:latest && docker logs -f test
cd96ff4cc2e98d59a618a7b32641ac144b22836445a8455358d2c71421e25cfa
s6-rc-compile: fatal: invalid /etc/s6-overlay/s6-rc.d/init-plex-chown/type: must be oneshot, longrun, or bundle

drewwats · 2023-04-17T15:33:06Z

I appreciate the help, y'all.

I have a current workaround using previous/dev/nightly builds that will work for now. I mostly wanted to make sure this didn't impact a bunch of other users, but it appears it's not going to be widespread.

I'd love to be able to switch back to latest tags in the future so hopefully this just works itself out naturally. If the develop and nighly branches run fine, my guess is it will; something is just weird with latest. Just for fun, I tried hardcoding latest to the full release tag (ghcr.io/linuxserver/plex:1.32.0.6918-6f393eda1-ls162) and it still errors.

For the record, nothing I know of changed on the Synology (DSM version, Docker version, configs, etc) except pulling latest container images this morning. Plex and everything was working great yesterday.

aptalca · 2023-04-17T15:34:30Z

Honestly I'm out of ideas.

Can you post your docker info? just for our reference?

Other than that, I'd recommend a good ole reboot to the system :-)

drewwats · 2023-04-17T15:36:37Z

I was just about to post docker version info, I'll post info too.

root@Synology:/Docker# docker version
Client:
 Version:           20.10.3
 API version:       1.41
 Go version:        go1.17.1
 Git commit:        55f0773
 Built:             Thu Jul 21 10:23:46 2022
 OS/Arch:           linux/amd64
 Context:           default
 Experimental:      true

Server:
 Engine:
  Version:          20.10.3
  API version:      1.41 (minimum version 1.12)
  Go version:       go1.17.1
  Git commit:       b487c8f
  Built:            Thu Jul 21 10:21:56 2022
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          v1.4.3
  GitCommit:        3fa00912415f3e9c6f82dd72119179d599efd13b
 runc:
  Version:          v1.0.0-rc93
  GitCommit:        31cc25f16f5eba4d0f53e35374532873744f4b31
 docker-init:
  Version:          0.19.0
  GitCommit:        ed96d00

root@Synology:/Docker# docker info
Client:
 Context:    default
 Debug Mode: false

Server:
 Containers: 17
  Running: 16
  Paused: 0
  Stopped: 1
 Images: 27
 Server Version: 20.10.3
 Storage Driver: btrfs
  Build Version: Btrfs v4.0
  Library Version: 101
 Logging Driver: db
 Cgroup Driver: cgroupfs
 Cgroup Version: 1
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs db fluentd gcplogs gelf journald json-file local logentries splunk syslog
 Swarm: inactive
 Runtimes: io.containerd.runc.v2 io.containerd.runtime.v1.linux runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: 3fa00912415f3e9c6f82dd72119179d599efd13b
 runc version: 31cc25f16f5eba4d0f53e35374532873744f4b31
 init version: ed96d00 (expected: de40ad0)
 Security Options:
  apparmor
 Kernel Version: 4.4.180+
 OSType: linux
 Architecture: x86_64
 CPUs: 4
 Total Memory: 19.39GiB
 Name: Synology
 ID: OSAN:7PNM:AFUU:XTYQ:GERC:E4U4:JTQS:GTTM:6G6K:7RSD:EAAK:IVKW
 Docker Root Dir: /volume1/@docker
 Debug Mode: false
 Registry: https://index.docker.io/v1/
 Labels:
 Experimental: false
 Insecure Registries:
  127.0.0.0/8
 Live Restore Enabled: false

WARNING: No kernel memory TCP limit support
WARNING: No cpu cfs quota support
WARNING: No cpu cfs period support
WARNING: No blkio weight support
WARNING: No blkio weight_device support
WARNING: No blkio throttle.read_bps_device support
WARNING: No blkio throttle.write_bps_device support
WARNING: No blkio throttle.read_iops_device support
WARNING: No blkio throttle.write_iops_device support

drewwats · 2023-04-17T15:38:56Z

Other than that, I'd recommend a good ole reboot to the system :-)

I tried the reboot before creating the bug report :)

drewwats · 2023-04-19T12:44:50Z

FYI, tried latest tag again with most recent build 1.32.0.6950-8521b7d99-ls163 and it worked fine again.

drewwats · 2023-04-19T13:02:17Z

DSM also upgraded to DSM 7.1.1-42962 Update 5 since the initial report. Closing the issue, thanks for your help!

drewwats closed this as completed Apr 19, 2023

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[BUG] Conflict with Synology Docker Version (20.10.3) #358

[BUG] Conflict with Synology Docker Version (20.10.3) #358

drewwats commented Apr 17, 2023 •

edited

github-actions bot commented Apr 17, 2023

thespad commented Apr 17, 2023

drewwats commented Apr 17, 2023

aptalca commented Apr 17, 2023

drewwats commented Apr 17, 2023

thespad commented Apr 17, 2023 •

edited

drewwats commented Apr 17, 2023

thespad commented Apr 17, 2023

aptalca commented Apr 17, 2023

drewwats commented Apr 17, 2023

j0nnymoe commented Apr 17, 2023

drewwats commented Apr 17, 2023

aptalca commented Apr 17, 2023

j0nnymoe commented Apr 17, 2023

drewwats commented Apr 17, 2023

drewwats commented Apr 17, 2023

aptalca commented Apr 17, 2023

drewwats commented Apr 17, 2023

drewwats commented Apr 17, 2023

drewwats commented Apr 19, 2023

drewwats commented Apr 19, 2023

[BUG] Conflict with Synology Docker Version (20.10.3) #358

[BUG] Conflict with Synology Docker Version (20.10.3) #358

Comments

drewwats commented Apr 17, 2023 • edited

Is there an existing issue for this?

Current Behavior

Expected Behavior

Steps To Reproduce

Environment

CPU architecture

Docker creation

Container logs

github-actions bot commented Apr 17, 2023

thespad commented Apr 17, 2023

drewwats commented Apr 17, 2023

aptalca commented Apr 17, 2023

drewwats commented Apr 17, 2023

thespad commented Apr 17, 2023 • edited

drewwats commented Apr 17, 2023

thespad commented Apr 17, 2023

aptalca commented Apr 17, 2023

drewwats commented Apr 17, 2023

j0nnymoe commented Apr 17, 2023

drewwats commented Apr 17, 2023

aptalca commented Apr 17, 2023

j0nnymoe commented Apr 17, 2023

drewwats commented Apr 17, 2023

drewwats commented Apr 17, 2023

aptalca commented Apr 17, 2023

drewwats commented Apr 17, 2023

drewwats commented Apr 17, 2023

drewwats commented Apr 19, 2023

drewwats commented Apr 19, 2023

drewwats commented Apr 17, 2023 •

edited

thespad commented Apr 17, 2023 •

edited