Skip to content

Docker container does not run on Synology DSM #74

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
MadWalnut opened this issue Mar 24, 2025 · 2 comments · May be fixed by #78
Open

Docker container does not run on Synology DSM #74

MadWalnut opened this issue Mar 24, 2025 · 2 comments · May be fixed by #78
Labels
bug Something isn't working

Comments

@MadWalnut
Copy link

I just noticed the Docker container does not run on Synology DSM.

Running the provided docker-compose.yaml results in tons of errors like these:

setfacl: var: Operation not supported
setfacl: var/cache: Operation not supported
setfacl: var/cache/prod: Operation not supported
setfacl: var/cache/prod/App_KernelProdContainer.php: Operation not supported
setfacl: var/cache/prod/App_KernelProdContainer.php.lock: Operation not supported
setfacl: var/cache/prod/App_KernelProdContainer.php.meta: Operation not supported
setfacl: var/cache/prod/App_KernelProdContainer.preload.php: Operation not supported
setfacl: var/log: Operation not supported

I found the exact same issue on a different project: elkarbackup/elkarbackup#581

I tried the workaround provided here but this does not seem to work for me. Editing and mounting the entrypoint.sh works, but $(uname -a) == *synology* matches directly on the host system, but not inside the Docker container because uname -a returns different things.

I am running Domain Watchdog on a different system for now. Not sure how you would want to proceed with this @maelgangloff. This does appear to be a distro-specific issue, but since this is the first time I have seen such behaviour (and I run lots of other containers on my Synology), I decided to report this anyway. Maybe you can think of a similar workaround or if not then this issue is at least a warning to future Synology / QNAP users. Hardcoding chown instead of setfacl in entrypoint.sh does work for what it's worth.
@maelgangloff maelgangloff added the bug Something isn't working label Mar 24, 2025
@maelgangloff
Copy link
Owner

Hello,

It's sad that this doesn't work on your platform.
Honestly, I'm not sure what specifically causes this issue with Synology devices.
I don't have any of these devices, so it will be difficult for me to test any fixes.
I'll leave this issue open while I wait for a fix.

Thanks for reporting this.

@zypA13510
Copy link

Workaround

Confirmed working on DSM v7.2.2.

docker-entrypoint.sh

Copy the content of docker-entrypoint.sh and modify this part:

-	setfacl -R -m u:www-data:rwX -m u:"$(whoami)":rwX var
-	setfacl -dR -m u:www-data:rwX -m u:"$(whoami)":rwX var
+	chown -R $(whoami):www-data var

docker-compose.yml

services:
  main:
    volumes:
      - ./docker-entrypoint.sh:/usr/local/bin/docker-entrypoint:ro
  worker:
    volumes:
      - ./docker-entrypoint.sh:/usr/local/bin/docker-entrypoint:ro

@zypA13510 zypA13510 linked a pull request May 5, 2025 that will close this issue
Draft
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix: setfacl operation not supported zypA13510/domain-watchdog
3 participants
@zypA13510 @MadWalnut @maelgangloff