Cor

I just did the same thing this morning. Used to running "Docker Safe New Perms" to allow writing in Kometa-created directories, and absentmindedly nuked my docker permissions. I tried the chmod and chown commands from above, but my dockers were still failing to start (and I didn't feel good about setting everything to 777 either). In case this helps someone, steps that worked for me to get back to a working setup are below. Key here is that I have the Appdata Backup running and creating backups nightly. 1. Disable Docker service (Settings>Docker>Enable Docker = No). 3. Refresh the page, and make sure your Docker directory is set correctly. 4. Click "Delete directory" and then click the orange "Delete" button. This will wipe the current Docker files and they'll be rebuilt with correct permissions later. 5. Just in case, make a backup of your current appdata directory somewhere else in case this doesn't work. I deleted everything in the original folder after this to make sure no incorrectly-permissioned stuck around to haunt me later. 6. Use the Appdata Backup plugin to restore your appdata files from the latest backup. 7. Go back to Settings>Docker and fill in the Docker directory field (mine is /mnt/nvme-cache/system/docker/docker/). 8. Select Enable Docker = Yes and click Apply. 9. Go to Apps>Previous Apps and reinstall your Docker containers. Back up your appdata! And if Docker Safe New Perms looks different and you're selecting disks for some reason, stop! It might be time for a break.