jaddel Posted June 22, 2021 Share Posted June 22, 2021 Hi Guys, I change my docker location from btrfs-image to directory and restored all my instances accordingly to the official restoring guide. Setting up the MariaDB container is causing the following issue: Command: root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='mariadb' --net='bridge' -e TZ="Europe/Berlin" -e HOST_OS="Unraid" -e 'PUID'='99' -e 'PGID'='100' -e 'MYSQL_ROOT_PASSWORD'='20Sjadsn' -p '3306:3306/tcp' -v '/mnt/user/appdata/mariadb':'/config':'rw' 'linuxserver/mariadb' 9767a34500f95fef1a159c923c44c4d09862c2c47902cba3996a864d367eb352 docker: Error response from daemon: OCI runtime create failed: container_linux.go:367: starting container process caused: exec: "/init": permission denied: unknown. The command failed. What I already tried: A clean setup of MariaDB from Community Apps with the same result. Fix filesystem permissions from Unraid Tools Reboot the server. tower-diagnostics-20210622-1310.zip Quote Link to comment
jaddel Posted June 22, 2021 Author Share Posted June 22, 2021 Update: I figured out, that setting new Permission to the whole disk somehow breaks the docker directory which causing the issue I described. Is this a bug? Quote Link to comment
Squid Posted June 22, 2021 Share Posted June 22, 2021 No, not a bug. You shouldn't ever run the New Permissions tool in such a way that it affects either the appdata share or a docker folder. Apps have their own unique permissions. In theory, you actually never need to run new permissions. Quote Link to comment
Recommended Posts
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.