Permissions on mounted /data volume not correct

[marclennox]

I'm running this instance with the /data directory mounted to the host machine with

-v /data/redis:/data

For some reason the permissions on the volume are not getting set properly despite the chown call in the Dockerfile, and therefore Redis pukes when trying to persist the DB.

Any ideas?

[tianon]

Does it work if you manually chown -R 999:999 /data/redis on your host?

(If you're wondering where the "999" came from, see docker run -it --rm redis id, which provides uid=999(redis) gid=999(redis) groups=999(redis).)

When you bind-mount, Docker doesn't touch the permissions of the directory that's being mounted in, which I'm guessing is the problem here.

[marclennox]

I will try.  I suspect the answer is yes.  However note that the MySQL and Postgres dockers work fine on this respect, presumably because they do the chown in an entry point script?  I'm thinking the redis docker just needs an entry point to do the permission change.—
Sent from Mailbox

On Thu, Aug 14, 2014 at 4:38 PM, Tianon Gravi [email protected]
wrote:

Does it work if you manually chown -R 999:999 /data/redis on your host?
(If you're wondering where the "999" came from, see docker run -it --rm redis id, which provides uid=999(redis) gid=999(redis) groups=999(redis).)

When you bind-mount, Docker doesn't touch the permissions of the directory that's being mounted in, which I'm guessing is the problem here.

Reply to this email directly or view it on GitHub:
#7 (comment)

[marclennox]

Confirmed that it worked by manually changing permissions to 999:999 on the
host

On 14 August 2014 19:38, Marc Lennox [email protected] wrote:

I will try. I suspect the answer is yes. However note that the MySQL and
Postgres dockers work fine on this respect, presumably because they do the
chown in an entry point script? I'm thinking the redis docker just needs
an entry point to do the permission change.
—
Sent from Mailbox https://www.dropbox.com/mailbox

On Thu, Aug 14, 2014 at 4:38 PM, Tianon Gravi [email protected]
wrote:

Does it work if you manually chown -R 999:999 /data/redis on your host?

(If you're wondering where the "999" came from, see docker run -it --rm
redis id, which provides uid=999(redis) gid=999(redis) groups=999(redis)
.)

When you bind-mount, Docker doesn't touch the permissions of the
directory that's being mounted in, which I'm guessing is the problem here.

—
Reply to this email directly or view it on GitHub
#7 (comment).

[ntharim]

This issue is kinda annoying. Possible to make it work like MySQL and Postgres?

[yosifkit]

Since we have already set a precedent with the other database images I think this would be ok. @tianon, do you agree?

I won't be able to get to it until after next week, but pull requests are welcome (just follow the examples @ntran13 cited, mysql and postgres).

[tianon]

Yeah, I think this is OK for now since we've already got the precedent set.

[yosifkit]

Sorry for the delay, but a PR to add the auto chowning the data dir is now up (with all the newer versions of redis to boot).

[ElvisTheKing]

same issue with mounted data dir when using with docker compose without specifying entry point:

for example with

redis:
  image: redis
  volumes:
    - ./data:/data/
  ports: ["6379:6379"]

actual command will be /entrypoint.sh redis which obviously wont work

[yosifkit]

The default CMD is redis-server, not redis, so it works just fine (/entrypoint.sh redis-server). Here is the latest image id:

$ docker images redis
REPOSITORY        TAG            IMAGE ID          CREATED           VIRTUAL SIZE
redis             latest         9216d5a4eec8      9 days ago        109.3 MB

[alexgorbatchev]

I'm having trouble getting this to work with docker machine & compose. Running docker in virtualbox env.

$ rm -fr tmp
$ docker-compose up
Starting test_redis_1
Attaching to test_redis_1
redis_1 | 1:M 17 Feb 20:06:08.714 # Can't open the append-only file: Permission denied
test_redis_1 exited with code 1

docker-compose.yml

version: "2"
services:
  redis:
    image: redis:3
    command: /entrypoint.sh redis-server --appendonly yes
    volumes:
      - ./tmp/redis:/data
    ports:
      - "6379:6379"

The ./tmp/redis folder is created but container can't write to it.

$ docker version
Client:
 Version:      1.10.1
 API version:  1.22
 Go version:   go1.5.3
 Git commit:   9e83765
 Built:        Thu Feb 11 19:14:21 2016
 OS/Arch:      darwin/amd64

Server:
 Version:      1.10.1
 API version:  1.22
 Go version:   go1.5.3
 Git commit:   9e83765
 Built:        Thu Feb 11 20:39:58 2016
 OS/Arch:      linux/amd64

$ docker-compose version
docker-compose version 1.6.0, build d99cad6
docker-py version: 1.7.0
CPython version: 2.7.9
OpenSSL version: OpenSSL 1.0.1j 15 Oct 2014

$ docker-machine version
docker-machine version 0.6.0, build e27fb87

[marclennox]

I've found when host mounting data volumes, you often have to pre-create them and set the permissions to 999:999. In some cases host mounting is very hard, such as with Postgres. I've stopped doing host-mounting entirely and have embraced volume containers, which make these problems go away.

[yosifkit]

If you still want to mount data to a shared folder on your Mac, then because the entrypoint script currently only does a chown and user drop-down you should be able to do something similar to #47 (comment).

[ralyodio]

when i pre-create the directory ./mongo-data with ownership of ubuntu:ubuntu and then I run docker-compose up --build it changes the owner to 999 and then docker gives a permission denied error.

[ahma0942]

Got the exact same problem as @chovy. Any fix to this?

[ralyodio]

https://stackoverflow.com/questions/61941469/my-local-volume-for-mongodb-gets-permission-deneied-when-running-docker-compose

[yosifkit]

@chovy, sorry I missed this. To use a local bind-mounted directory, you need to pre-create the directory (as you do) and then add user to the MongoDB service in the compose file with the ids of the owner of the directory (i.e. your ubuntu user and group; e.g. user: "1000:1000").

If you do not pre-create the directory locally, then docker will create it as root owned when the container starts (and then the mongo container will be unlikely to have access and fail to start).

(The same applies to a bind-mounted redis data directory as well)

https://docs.docker.com/compose/compose-file/#domainname-hostname-ipc-mac_address-privileged-read_only-shm_size-stdin_open-tty-user-working_dir

[Yingsheng-eroad]

Have the same issue as @chovy, but mine is postgres. I answered the question in StackOverflow.

[neuronflow]

same issue with redis and docker-compose..I run this setup on 3 machines and only one is affected on a regular basis, very weird.

[Yingsheng-eroad]

same issue with redis and docker-compose..I run this setup on 3 machines and only one is affected on a regular basis, very weird.

This is my solution. Check if it helps.
https://stackoverflow.com/questions/61941469/my-local-volume-for-mongodb-gets-permission-deneied-when-running-docker-compose/62185391#62185391

[ghost]

I had the same problem.

create a .dockerignore file at the root of the building containing your data folder