redis: Permissions on mounted /data volume not correct

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?

About this issue

Original URL
State: closed
Created 10 years ago
Comments: 20 (7 by maintainers)

Commits related to this issue

🛠️ `Neighborhood`: Use own devcontainer and persist user data (#1419) * Add `bundle install` and `bin/setup` to Dockerfile The `bin/setup` will fail due to not having the database containers up, ... — committed to zinc-collective/convene by daltonrpruitt a year ago

Most upvoted comments

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.

marclennox on Feb 17, 2016

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.

ralyodio on Sep 21, 2019

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.

tianon on Aug 14, 2014