Cannot access files on mounted volume about docker-teamspeak3 HOT 11 CLOSED

Did u use old files from another TS3-Install or was it a "fresh" install (/data/teamspeak was empty before running the container)?
And can u maybe post an "ls -all" from your /data/teamspeak/-directory?

from docker-teamspeak3.

First at all - thank you for your fast reply.
I used the files from another TS3-Install - I wanted to keep my old configurations and the old database.
The permissions are:

from docker-teamspeak3.

Here is the command I used to create your docker image.

from docker-teamspeak3.

So, in general you dont need to keep the complete TS3-folder and put it into the /data/teamspeak-dir, because all runtime-files of the server are meant to stay inside the actual TS3-container. (Like the startscripts)
In the current version the files are created as root by the container, so you could try to "chown -R root /data/teamspeak". (I just started today so they will not be created as root, just need some more time updating the README)
You can also try to delete the logs/-folder so the container can create it with the correct permissions himself (hopefully)

from docker-teamspeak3.

Does the server in the docker image create the folder for the logfiles inside my /data/teamspeak or in a custom folder inside the docker image?
I changed the owner to root:root, but no success - I also removed all other files but now i get a critical error.
2016-02-18 21:47:01.429623|CRITICAL|VirtualSvrMgr | | unable to start filemanager, while creating directory : files failed

But if you also dont know any more things which I can try, I will do some more research and try to fix this and will get back to you ^^

from docker-teamspeak3.

Sorry, i never tried to import old data ^^
Seems like there is still a permission problem and he cant create the files-folder now.
The container should create the logs inside your /data/teamspeak-folder (Because /teamspeak3 inside the container is mapped to it).

from docker-teamspeak3.

Mh yes, there is a problem with the permissions ... didnt see this error message until now ...
mkdir: cannot create directory '/teamspeak3/files': Permission denied

from docker-teamspeak3.

In the new beta-branch i implemented an ENV-variable to set the UID of the internal user in the actual container, maybe it is of any help:
sudo docker run --name=ts3 -d -e TS3_UID=1000 -v /home/devalx/docker/ts3-test:/data/ts3 devalx/docker-teamspeak3:beta
(Make sure to keep a backup of your db ;-)
Keep in mind that the parent-folder (in my example ts3-test) is writable/owned by the specific UID on the host.
Also i am not sure what happens if u specify UID 1111 and there is no actual user with UID 1111 on the host machine.

from docker-teamspeak3.

I figured out why i got problems with my permissions.
I use fedora server as host system and fedora has SElinux enabled.

Here I found the solution.
https://linuxconfig.org/how-to-share-data-between-a-docker-container-and-host-system-using-volumes

I have to create the docker image with the --privileged=true flag.

Now everything works like a charm 👍

Thank you very much for your help @devalx

from docker-teamspeak3.

You are welcome, thank you for sharing the solution!
I never used them but maybe the :z|:Z options help you in this case too and you dont need to privilige the whole container, see https://docs.docker.com/engine/userguide/containers/dockervolumes/

from docker-teamspeak3.

Thanks, the solution with the labels is working and is even better. Didnt see, that there is this option.
docker run --name ts3 -d -p 9987:9987/udp -p 30033:30033 -p 10011:10011 -v /data/teamspeak:/teamspeak3:z devalx/docker-teamspeak3

Thank you very much

from docker-teamspeak3.