Suwayomi-Server-docker: Unable to run at DSM 7.1 (Permission Error)
Hi guys, trying to deploy on my synology NAS yet suwayomi refuses to start up. Seems some permission issues but have no idea how to fix it.
the log was very short and raises following error
Suwayomi data location inside the container: /home/suwayomi/.local/share/Tachidesk error: cannot create /home/suwayomi/startup/server-reference.conf Permission denied mv: cannot stat ‘/home/suwayomi/startup/server-reference.conf’: Permission denied
command used was docker run -p 127.0.0.1:4567:4567 ghcr.io/suwayomi/tachidesk:preview
actually tried docker run -p 127.0.0.1:4567:4567 ghcr.io/suwayomi/tachidesk:latest as well but also the same error raised.
About this issue
- Original URL
- State: open
- Created 2 years ago
- Comments: 39 (5 by maintainers)
my solution is changing the binding folder ,the default is - ./data:/home/suwayomi/.local/share/Tachidesk, I changed the folder /home/suwayomi/.local/share/Tachidesk to /root/.local/share/Tachidesk ,and the docker works normally.
Above is invalid, it needs to be
I’m having the exact same issue. I’m running several other containers with service accounts just fine but something with this image is failing trying to create the files.
Scenarios:
No mounted folder This “works” since the files are created in memory within the container but of course any configuration is lost after the container restart
Mount to folder while using service account I created a folder at /volume1/docker/tachidesk/files which is mounted to /home/suwayomi/.local/share/Tachidesk (Synology convention is that the docker compose file is written to /volume1/docker/tachidesk/compose.yml, so created the /files to hold the actual config)
Created a service account named svc.tachidesk and gave it full control of the folder

Determined the UID/PID of the newly created service account and added it to the docker-compose:
When I run the container the log shows failures trying to create the config:
The fact that its asking if it should replace the file seems odd to me, as that should only occur in a command line scenario. There must be something unique with the way that this code works while its trying to create the files.
ADDITIONAL INFO: I changed the container to run in privileged mode with the “privileged: true” flag and received the same errors in the log.
version: ‘3.7’ services: suwayomi: image: ghcr.io/suwayomi/tachidesk:latest environment: - TZ=Etc/UTC # Use TZ database name from https://en.wikipedia.org/wiki/List_of_tz_database_time_zones # Comment these out if you do not use the flaresolverr container at the bottom of this file - FLARESOLVERR_ENABLED=true - FLARESOLVERR_URL=http://flaresolverr:8191 volumes: - /volume1/docker/tachidesk-docker/config:/root/.local/share/Tachidesk ports: - “4567:4567” restart: on-failure:3
here’s my docker-compose yaml