[BUG] crash on qnap due to broken chmod

[klepek]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

startup crashes due to issue with chmod on qnap (see: linuxserver/docker-swag#514)
application log:

... s6-rc: warning: unable to start service init-permissions: command exited 1

Expected Behavior

it starts correctly

Steps To Reproduce

1. on qnap with container station
2. with default config
3. run package
4. see container logs for error

Environment

- OS: qnap (latest stable) 
- How docker service was installed: Container station

CPU architecture

x86-64

Docker creation

default from documentation

Container logs

`using keys found in /config/keys
chmod: changing permissions of '/etc/logrotate.d/acpid': Bad address
chmod: changing permissions of '/etc/logrotate.d/nginx': Bad address
chmod: changing permissions of '/etc/logrotate.d/php-fpm': Bad address
chmod: changing permissions of '/etc/logrotate.d/php-fpm83': Bad address
chmod: changing permissions of '/config/nginx/site-confs': Bad address
chmod: changing permissions of '/config/nginx/site-confs/default.conf.sample': Bad address
chmod: changing permissions of '/config/nginx/site-confs/default.conf': Bad address
chmod: changing permissions of '/config/nginx/nginx.conf.sample': Bad address
chmod: changing permissions of '/config/nginx/ssl.conf.sample': Bad address
chmod: changing permissions of '/config/nginx/nginx.conf': Bad address
chmod: changing permissions of '/config/nginx/ssl.conf': Bad address
chmod: changing permissions of '/config/nginx/dhparams.pem': Bad address
chmod: changing permissions of '/config/nginx/resolver.conf': Bad address
chmod: changing permissions of '/config/nginx/worker_processes.conf': Bad address
s6-rc: warning: unable to start service init-permissions: command exited 1`

[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.

[LinuxServer-CI]

This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.

[LinuxServer-CI]

This issue is locked due to inactivity