February 10Feb 10 I am troubleshooting an issue where my docker containers become unreachable after they are rebooted. I found that if I manually change the owner on the /mnt/user/appdata/containername to nobody:users and set the permissions to 775 then reboot the container, it works again until the next reboot.First, how do I find out what is causing these permissions to change? and Second, is there a better way to restore the owner/permissions correctly?
February 10Feb 10 Community Expert Each container should manage its own appdata owner/permissions. In fact, we usually say don't mess with that yourself. That is why Docker Safe New Perms exists, because it won't modify appdata.Maybe you should just delete appdata and start over, and leave that alone.
February 10Feb 10 Author 34 minutes ago, trurl said:Each container should manage its own appdata owner/permissions. In fact, we usually say don't mess with that yourself. That is why Docker Safe New Perms exists, because it won't modify appdata.Maybe you should just delete appdata and start over, and leave that alone.What is the safe way to re-create the appdata folder without losing all my containers?
February 10Feb 10 Author Also, I saw someone mention their appdata backup plugin was causing their issues. Do these settings look correct?
February 11Feb 11 Author Solution I ended up backing up the config inside each container, turned off Docker, renamed appdata to appdata-old, turned Docker back on and restored the backup within each container. That seemed to work fine.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.