I had this container running periodic backup and kept UpToDate with watchtower on the latest tag
but I noticed backup failing with permission denined.
after investigation I noticed that the root user in the container does not have permissions to any files or folders.
not just mounted folders that permissions can be messed up but to the container root directory.
[migrations] started
[migrations] no migrations found
───────────────────────────────────────
██╗ ███████╗██╗ ██████╗
██║ ██╔════╝██║██╔═══██╗
██║ ███████╗██║██║ ██║
██║ ╚════██║██║██║ ██║
███████╗███████║██║╚██████╔╝
╚══════╝╚══════╝╚═╝ ╚═════╝
Brought to you by linuxserver.io
───────────────────────────────────────
To support LSIO projects visit:
https://www.linuxserver.io/donate/
───────────────────────────────────────
GID/UID
───────────────────────────────────────
User UID: 99
User GID: 100
───────────────────────────────────────
Linuxserver.io version: 1.4.5-r0-ls112
Build-date: 2024-06-27T04:42:22+00:00
───────────────────────────────────────
***** Upgrading config file if required *****
/etc/rsnapshot.conf file is already up to date.
***** Validating config file *****
K
[custom-init] No custom files found, skipping...
[ls.io-init] done.
Is there an existing issue for this?
Current Behavior
I had this container running periodic backup and kept UpToDate with watchtower on the
latest
tagbut I noticed backup failing with permission denined. after investigation I noticed that the root user in the container does not have permissions to any files or folders. not just mounted folders that permissions can be messed up but to the container root directory.
I tested releases and found that this happened after the recent update from 1.4.5-r0-ls109 to 1.4.5-r0-ls110
This could be due to the rebase to alpine 3.20
Expected Behavior
on image tag 1.4.5-r0-ls109 and older
root can see files as expected
Steps To Reproduce
ls -l /
Environment
CPU architecture
x86-64
Docker creation
Container logs