-
Notifications
You must be signed in to change notification settings - Fork 574
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
*** FATAL CONFIG FILE ERROR *** passing as parameter redis.conf file #67
Comments
The error is definitely misleading. I noticed that the volume path was not an absolute path and so that seemed to fix it. Here is what I did: -docker run -v redis.conf:/usr/local/etc/redis/redis.conf --name node redis redis-server /usr/local/etc/redis/redis.conf
+docker run -v "$PWD"/redis.conf:/usr/local/etc/redis/redis.conf --name node redis redis-server /usr/local/etc/redis/redis.conf If your volume is not an absolute path on the left (beginning in a $ docker volume ls
DRIVER VOLUME NAME
local redis.conf |
@yosifkit you are right! It works if I pass the absolute path of my redis.conf file 😄 However, the alternative passing the port number as parameter with the -p flag still does not work and I get the same error:
|
It looks like all redis flags are |
It works with --port. Thank you very much! 😄 |
I am trying to create a Redis cluster node passing as parameter my own redis.conf file with the following configuration:
I am running the following command to create the cluster node, which seems to be correct according with the documentation:
But I am getting the following error:
If I create my own Dockerfile to add the configuration file inside, it works perfect. But this is not the solution that I pursuit due I need to create nodes with different port numbers.
If I remove the port number from my configuration file, then I create my custom image named "redis-cluster-node" and finally I run the following command to pass the port as parameter:
I get the following error:
My configuration file works fine with the original project when I create a cluster node, so I presume the problem is related with the docker image itself or maybe I am missing something.
Can you help me with this? Thanks in advance! 😃
The text was updated successfully, but these errors were encountered: