[BUG] Error on Synology docker after container is created.

[Ciechom]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

I keep getting these errors after the swag container starts. It started after I updated docker to the newest version on synology (Container manager: 24.0.2-1606).
Error response from daemon: client version 1.52 is too new. Maximum supported API version is 1.43

When I first ran a container created on a previous version of docker it worked properly, only after updating to the newest version of swag container it got broken. (Recreating the old version of swag on current docker version doesn't work).

This: "Error response from daemon: client version 1.52 is too new. Maximum supported API version is 1.43" line in log keeps repeating once every minute after starting the container.

The docker-compose I provided is censored, the container previously was getting created and started without any problems.

Expected Behavior

The container would start and work properly.

Steps To Reproduce

On latest version of container manager on synology start a swag container from docker-compose or portainer.

Environment

- OS: Synology DSM 7.3.1-86003
- How docker service was installed: newest version of container manager installed through the "package manager" - I'm not sure if it's the proper name, but it's the only was to install docker on synology AFAIK.

CPU architecture

x86-64

Docker creation

services:
  swag:
    image: linuxserver/swag:latest
    container_name: swag
    cap_add:
      - NET_ADMIN
    environment:
      - PUID=1026
      - PGID=101
      - TZ=Europe/Warsaw
      - URL=yy.xx
      - VALIDATION=dns
      - SUBDOMAINS=wildcard #www,ftp,cloud
      - DNSPLUGIN=cloudflare #optional
      - PROPAGATION= #optional
      - EMAIL=yy@yy.xx #optional
      - ONLY_SUBDOMAINS=false #optional
      - EXTRA_DOMAINS= #optional
      - STAGING=false #optional used for testing only
      - DISABLE_F2B= #optional
      - SWAG_AUTORELOAD=true #optional
      - DOCKER_HOST=dockerproxy
      - MAXMINDDB_LICENSE_KEY=<license_key>
      - MAXMINDDB_USER_ID=<id>
      - DOCKER_MODS=linuxserver/mods:universal-docker|linuxserver/mods:swag-auto-proxy|linuxserver/mods:swag-maxmind|linuxserver/mods:swag-dashboard
    volumes:
      - /volume2/docker/config/swag:/config
    ports:
      - 4443:443
      - 44380:80 #optional
      - 4443:443/udp #optional
      - 81:81 #dashboard local only
    restart: unless-stopped

Container logs

[mod-init] Running Docker Modification Logic
[mod-init] Adding linuxserver/mods:universal-docker to container
[mod-init] Downloading linuxserver/mods:universal-docker from lscr.io
[mod-init] Installing linuxserver/mods:universal-docker
[mod-init] linuxserver/mods:universal-docker applied to container
[mod-init] Adding linuxserver/mods:swag-auto-proxy to container
[mod-init] Downloading linuxserver/mods:swag-auto-proxy from lscr.io
[mod-init] Installing linuxserver/mods:swag-auto-proxy
[mod-init] linuxserver/mods:swag-auto-proxy applied to container
[mod-init] Adding linuxserver/mods:swag-maxmind to container
[mod-init] Downloading linuxserver/mods:swag-maxmind from lscr.io
[mod-init] Installing linuxserver/mods:swag-maxmind
[mod-init] linuxserver/mods:swag-maxmind applied to container
[mod-init] Adding linuxserver/mods:swag-dashboard to container
[mod-init] Downloading linuxserver/mods:swag-dashboard from lscr.io
[mod-init] Installing linuxserver/mods:swag-dashboard
[mod-init] linuxserver/mods:swag-dashboard applied to container
[migrations] started
[migrations] 01-nginx-site-confs-default: skipped
[migrations] 02-swag-old-certbot-paths: skipped
[migrations] done
───────────────────────────────────────
      ██╗     ███████╗██╗ ██████╗
      ██║     ██╔════╝██║██╔═══██╗
      ██║     ███████╗██║██║   ██║
      ██║     ╚════██║██║██║   ██║
      ███████╗███████║██║╚██████╔╝
      ╚══════╝╚══════╝╚═╝ ╚═════╝
   Brought to you by linuxserver.io
───────────────────────────────────────
To support the app dev(s) visit:
Certbot: https://supporters.eff.org/donate/support-work-on-certbot
To support LSIO projects visit:
https://www.linuxserver.io/donate/
───────────────────────────────────────
GID/UID
───────────────────────────────────────
User UID:    1026
User GID:    101
───────────────────────────────────────
Linuxserver.io version: 5.1.0-ls419
Build-date: 2025-11-15T03:44:07+00:00
───────────────────────────────────────
    
using keys found in /config/keys
Variables set:
PUID=1026
PGID=101
TZ=Europe/Warsaw
URL=yyy.xx
SUBDOMAINS=wildcard
EXTRA_DOMAINS=
ONLY_SUBDOMAINS=false
VALIDATION=dns
CERTPROVIDER=
DNSPLUGIN=cloudflare
EMAIL=yy@yy.xx
STAGING=false
Using Let's Encrypt as the cert provider
SUBDOMAINS entered, processing
Wildcard cert for yy.xx will be requested
E-mail address entered: yy@yy.xx
dns validation via cloudflare plugin is selected
Certificate exists; parameters unchanged; starting nginx
The cert does not expire within the next day. Letting the cron script handle the renewal attempts overnight (2:08am).
**** adding libmaxminddb to package install list ****
**** installing docker and docker compose ****
Error response from daemon: client version 1.52 is too new. Maximum supported API version is 1.43
Copying over docker and docker-compose binaries
**** Applying the SWAG dashboard mod... ****
**** Remote docker service dockerproxy will be used ****
**** Adding goaccess to package install list ****
**** libmaxminddb already installed, skipping ****
**** Applied the SWAG dashboard mod ****
[pkg-install-init] **** Installing all mod packages ****
fetch http://dl-cdn.alpinelinux.org/alpine/v3.22/main/x86_64/APKINDEX.tar.gz
fetch http://dl-cdn.alpinelinux.org/alpine/v3.22/community/x86_64/APKINDEX.tar.gz
(1/2) Installing goaccess (1.9.4-r0)
(2/2) Installing libmaxminddb (1.9.1-r0)
Executing busybox-1.37.0-r19.trigger
OK: 189 MiB in 223 packages
Applying the maxmind mod...
Applied the maxmind mod
[custom-init] No custom files found, skipping...
Auto-reload: Watching the following folders for changes to .conf files:
/config/nginx
[ls.io-init] done.
Server ready
Error response from daemon: client version 1.52 is too new. Maximum supported API version is 1.43
Error response from daemon: client version 1.52 is too new. Maximum supported API version is 1.43

[github-actions]

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

[thespad]

Synology still ships Docker v24, which has been EOL for a long time. The universal-docker mod tracks the latest upstream Docker version, which is now v29, and that requires at least v25 for API compatibility. As a result your docker service on the host is now too old for the docker client in the container to be able to communicate with.

There's not a lot we can do to fix this, but you can pin to an older version of the mod such as universal-docker-28.5.2-2.40.3

[Ciechom]

Synology still ships Docker v24, which has been EOL for a long time. The universal-docker mod tracks the latest upstream Docker version, which is now v29, and that requires at least v25 for API compatibility. As a result your docker service on the host is now too old for the docker client in the container to be able to communicate with.

There's not a lot we can do to fix this, but you can pin to an older version of the mod such as universal-docker-28.5.2-2.40.3

Thank you for the answer, is there a good place to find all of the universal-docker mod versions?

[thespad]

https://hub.docker.com/r/linuxserver/mods/tags?name=universal-docker-2 (without the 2 you'll get docker-in-docker mod versions too, and you wouldn't want to back 3+ years anyway)

[drizuid]

I'm on mobile so can't provide you the answer to your above question, however, i wanted to chime in and suggest literally anything other than synology. it's a great NAS, but it's bad for everything else. the kernel has been eol for years, docker version is eol, synology does not care about things outside of the NAS function. A raspi 4 or 5 would do better than what you currently have and be less prone to security vulnerabilities (because you can actually get updates) just something to consider

[Ciechom]

I'm on mobile so can't provide you the answer to your above question, however, i wanted to chime in and suggest literally anything other than synology. it's a great NAS, but it's bad for everything else. the kernel has been eol for years, docker version is eol, synology does not care about things outside of the NAS function. A raspi 4 or 5 would do better than what you currently have and be less prone to security vulnerabilities (because you can actually get updates) just something to consider

I'm in the process of saving money for a hdd to deploy a proxmox server because of the stuff that annoys me in synology.

https://hub.docker.com/r/linuxserver/mods/tags?name=universal-docker-2 (without the 2 you'll get docker-in-docker mod versions too, and you wouldn't want to back 3+ years anyway)

Thanks, i made it work again by changing it to the last 28.xx version :)

Finally a very good reason to speed up the proxmox server deployment ^^