captainjee

This might have been brought up before, though I wasn't able to find it in this thread. I need a mysql DB and why not use this mariadb docker, so I installed it in Unraid. It couldn't start though, complaining that it wasn't able to write into /tmp/<somerandomname>, due to "Permission denied". As a quick fix I gave everyone full permissions to everything under the mariadb docker folder in appdata (777). To my surprise it did not change anything. Then I went to delete the docker.img file, create a new one, and added all my containers again, and now the mariadb docker was working (with default permissions on the appdata folder, 99:100 755). I started to make use of the mariadb for an application. Thinking it was solved I came back today and started the mariadb docker only to be met by the same error - it can't write to the /tmp folder. Which is weird as that folder is not being mapped as a volume in the configuration of the container, which I actually just noticed now. I just tried adding this as a volume, and that seemed to fix that issue. Instead I'm now met with another error upon starting the container: [ERROR] Can't start server : Bind on unix socket: Permission denied I realized this is caused by the fact that the server wants to bind a socket on 0.0.0.0, which of course shouldn't be allowed for a container to do. Instead I created a .cnf file in the config folder to bind only to the container's own IP. This seems to solve the issue as it now creates the socket on the IP - but still isn't able to bind on the unix socket. I now get these logs: 2026-02-07 18:17:06 0 [Note] Server socket created on IP: 'xx.xx.xx.xx', port: '3306'. 2026-02-07 18:17:06 0 [ERROR] Can't start server : Bind on unix socket: Permission denied 2026-02-07 18:17:06 0 [ERROR] Do you already have another server running on socket: /run/mysqld/mysqld.sock ? Actually I'm wrong in the above - it is the unix socket it cannot bind on, not the IP. So what's up with this mariadb container - what am I doing wrong? Why can't it do it's very basic thing (its a mariadb container) to start the mariadb service, binding on the socket only found within the container itself? I actually have a hard time believing this, it seems pretty pointless to me, uploading a container like this - I might as well build my own mysql/mariadb container then. Please correct me if I'm wrong !