Version 7+ cannot handle non-localhost connections as protected mode is on and authentication is not supported about docker-redis-cluster HOT 8 CLOSED

Just curious, is there a reason why you wouldn't make the change to redis-cluster.tmpl in this repo? I believe this breaking change in 7.x is effectively the cause:

Modifying the bind parameter to a non-default value will no longer implicitly disable protected-mode (#9034)

So this project has been disabling protected-mode since redis version 3.2, and more depend on it being off than on.

from docker-redis-cluster.

Resolved in d5a8e12
New images will be published shortly

from docker-redis-cluster.

@jordyvanvorselen The simplest solution right now is that either you go back to a 6.2.x image, or you clone the repo and you update the file redis-cluster.tmpl to remove protected mode for your own image you build and use.

The config parser is being rewritten, but no date on when that is done to enable easier config modifications rather then to build your own image

from docker-redis-cluster.

6.2.x image does not seem to work for me. The follow command does not start any container successfully, nor does it give any errors. Any idea why?
docker run -d -e "IP=0.0.0.0" -p 7000-7005:7000-7005 grokzen/redis-cluster:6.2.10 --protected-mode no

The docker logs seems to suggest that there is no --protected-mode or I did not add the option in the right way.
❯ docker logs 235315420ba7
/docker-entrypoint.sh: 102: exec: --protected-mode: not found

from docker-redis-cluster.

@ghShu If you look at how all processes is started, you will see that the entrypoint that dockers starts is not redis-server command where your extra argument would be passed along into, but it starts a bash script and ignores any additional cli arguments that would otherwise be passed in to the running process by docker

from docker-redis-cluster.

Just curious, is there a reason why you wouldn't make the change to redis-cluster.tmpl in this repo? I believe this breaking change in 7.x is effectively the cause:

Modifying the bind parameter to a non-default value will no longer implicitly disable protected-mode (#9034)

So this project has been disabling protected-mode since redis version 3.2, and more depend on it being off than on.

I agree. @Grokzen even mentioned in the README that this is not a production container at all and is for quick use for demo/presentation/development, so we can safely enable this for this repository.

Now, having that said, @Grokzen can you add the protected-mode on in the redis.conf and publish a new release to fix this issue as a hotfix? Then you can make things configurable later on.

from docker-redis-cluster.

Works! Thanks a lot @Grokzen!

from docker-redis-cluster.

Works well! Thanks @Grokzen, awesome 👍

from docker-redis-cluster.