[GH-ISSUE #506] Add a configuration item to set unix domain socket files permissions for docker #286

New Issue

zhus · 2026-04-08T16:51:44+03:00

zhus commented

2026-04-08 16:51:44 +03:00

Originally created by @wayilive on GitHub (Dec 24, 2024).
Original GitHub issue: https://github.com/sigoden/dufs/issues/506

Add a configuration item to set unix domain socket files permissions, this feature exists in alist, alist's configure file has a configuration item 'unix_file_perm' and usually has a value '0666'.

I want to combine using dufs and nginx in one docker compose file and share the unix domain socket between container and the host.

Originally created by @wayilive on GitHub (Dec 24, 2024). Original GitHub issue: https://github.com/sigoden/dufs/issues/506 Add a configuration item to set unix domain socket files permissions, this feature exists in alist, alist's configure file has a configuration item 'unix_file_perm' and usually has a value '0666'. I want to combine using dufs and nginx in one docker compose file and share the unix domain socket between container and the host.

zhus closed this issue

2026-04-08 16:51:44 +03:00

zhus commented

2026-04-08 16:51:45 +03:00

@sigoden commented on GitHub (Dec 24, 2024):

We will not support this feature. This configuration is too trivial.

Please change the file permissions manually after Dufs creates the socket file.

Another option is to change the umask settings. The default file permissions for a Unix domain socket path created by a Rust program are determined by the umask setting.

@sigoden commented on GitHub (Dec 24, 2024): We will not support this feature. This configuration is too trivial. Please change the file permissions manually after Dufs creates the socket file. Another option is to change the umask settings. The default file permissions for a Unix domain socket path created by a Rust program are determined by the umask setting.

zhus commented

2026-04-08 16:51:45 +03:00

@Puqns67 commented on GitHub (Apr 19, 2025):

PS: In systemd.service, you can add this line to change UNIX socket permissions after dufs start.

This assumes that your UNIX socket is under /run/dufs, and you can modify it yourself.

ExecStartPost=/usr/bin/bash -c '/usr/bin/sleep 1; for file in /run/dufs/*; do if [ -S "$file" ]; then /usr/bin/chmod 0660 "$file"; fi; done'

@Puqns67 commented on GitHub (Apr 19, 2025): PS: In systemd.service, you can add this line to change UNIX socket permissions after dufs start. * This assumes that your UNIX socket is under `/run/dufs`, and you can modify it yourself. ```service ExecStartPost=/usr/bin/bash -c '/usr/bin/sleep 1; for file in /run/dufs/*; do if [ -S "$file" ]; then /usr/bin/chmod 0660 "$file"; fi; done' ```

zhus referenced this issue

2026-04-08 16:53:24 +03:00

[PR #286] [MERGED] fix: use DUFS_CONFIG to specify the configuration path #550

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: sigoden/dufs#286