search

linuxserver / docker-jackett

GNU General Public License v3.0
394 stars 95 forks source link

docker-jackett chowns mounted directories/volumes unnecessarily? #37

Closed n1nj4888 closed 6 years ago

n1nj4888 commented 6 years ago

docker-jackett seems to unnecessarily “chown” mounted directories to the docker-jackett container PUID?

For example, when the docker-jackett container is started, it changes the owner of say directory X (a mounted directory in the container) to the PUID of the docker-jackett container, yet this same directory maybe also used by other docker containers (say docker-container-B) as well... this results in a strange situation where, if docker-container-B starts after the docker-jackett container and then writes to the same directory, all files are owned in the directory by docker-jackett PUID?

Using Synology Docker...

tobbenb commented 6 years ago

Can't you use the same UID on both containers?

n1nj4888 commented 6 years ago

I could but that’s not exactly solving the problem. I’d rather run each container with its own UID to better control which container can do what.

n1nj4888 commented 6 years ago

Perhaps a better way would be to have an environment variable called DONT_CHANGE_DIR_OWNERSHIP or similar such that, when changed to true, it does not chown any of the configured mounted directories accept /config ?

sparklyballs commented 6 years ago

I could but that’s not exactly solving the problem

your setup having separate PxID for each container is creating the problem