Redis configuration bind mount permissions

[mut3]

On the Redis dockerhub page, this line is given as a means of using a host machine stored configuration file as the redis config at run.

# docker run -v /myredis/conf/redis.conf:/usr/local/etc/redis/redis.conf --name myredis redis /usr/local/etc/redis/redis.conf

however if i run

# docker run  -v /redis/conf/redis1.conf:/usr/local/etc/redis/redis.conf redis /usr/local/etc/redis/redis.conf

i get

/entrypoint.sh: line 9: /usr/local/etc/redis/redis.conf: Permission denied

if I run

# docker run  -v /redis/conf/redis1.conf:/usr/local/etc/redis/redis.conf redis 

a default configured redis container launches perfectly, but i want to use my configuration file without writing my own Dockerfile

CentOS 7
Docker 1.6.2
redis:latest

I did a bunch of troubleshooting and hacked around to get it working, Ill document that below to leave a clear division between problem and workaround/hack.

[mut3]

I had previously had issues bind-mounting other containers due to SELinux, but I had expected that and had already executed

# chcon -Rt svirt_sandbox_file_t /redis/

on my local machine. I confirmed that this was not a SELinux caused issue with

# setenforce 0

and then trying to launch the same command. I got the same result.

For the following problem solving steps I will note a few things:

• I am using the include functionality of redis conf files, so I actually want to mount a directory
• After realizing that the location of the conf files didn't matter as long as you pointed the server at them i decided to use the container dir /redis-settings/ as my mount point to make my life easier

Some short googling found me some useful older issues:

• Run as user "elasticsearch" elasticsearch#5
• invalid line return character in docker-entrypoint.sh prevents from using a data volume elasticsearch#35
• Add ability to mount volume as user other than root moby/moby#2259

That last one was the most helpful.

I guessed (correctly) that this was a permission issue within the container so:

# docker run --rm --name red-1-container -p 6379:6379 -v /redis/conf/:/redis-settings/ chown -Rv redis:redis /redis-settings/ 
ownership of `/redis-settings/redis.conf' retained as redis:redis
ownership of `/redis-settings/redis2.conf' retained as redis:redis
ownership of `/redis-settings/redis1.conf' retained as redis:redis
ownership of `/redis-settings/' retained as redis:redis

The owner of the directory was correct and the files are where they are supposed to be, what's the issue then?

# docker run --rm --name red-1-container -p 6379:6379 -v /redis/conf/:/redis-settings/ redis whoami
root

well thats not right. I'm supposed to be running the server as redis:redis.

And the winning command is

# docker run --rm --name red-1-container -p 6379:6379 -v /redis/conf/:/redis-settings/ redis gosu redis:redis redis-server /redis-settings/redis1.conf

I'm not sure exactly where the problem resides, but redis does not seem to be taking the custom config file and stepping down correctly and is instead trying to do something as root when the container firmly wants that action to be executed by redis:redis.

[mut3]

hm should this issue have been opened here https://github.com/docker-library/redis instead?

[yosifkit]

Oh, probably 😐. I think your PR to fix the docs will be sufficient. 'Twas just the missing redis-server anyway.