Disabling protected mode (v.7+) #149
-
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
Interesting, this was a new security feature added that i was not aware of in redis 7.0 The short answer is no, there is no feature right now to "simply disable" it via some flag or something. But you have a few options to help you out in the short term. One is to modify this file https://github.com/Grokzen/docker-redis-cluster/blob/master/redis-cluster.tmpl to include the config option you want, rebuild the image to you'r own copy and use that one instead. This would map to suggestion The second alternative would be to volume map in your own configuration files that you generate separate where you include all the configuration you want for your instances A third alternative is to fork https://github.com/Grokzen/docker-redis-cluster/blob/master/docker-entrypoint.sh and to modify the entrypoint. It might even be possible to use another entrypoint command all together that you can make before running this script. A fourth alternative is that after you start your container, you run a A fifth alternative might be that if you run docker-compose solution, there might be options to use different command or entrypoints or to simply just rebuild the image to what you need. |
Beta Was this translation helpful? Give feedback.
Interesting, this was a new security feature added that i was not aware of in redis 7.0
The short answer is no, there is no feature right now to "simply disable" it via some flag or something.
But you have a few options to help you out in the short term. One is to modify this file https://github.com/Grokzen/docker-redis-cluster/blob/master/redis-cluster.tmpl to include the config option you want, rebuild the image to you'r own copy and use that one instead. This would map to suggestion
2.
from the above mentioned suggestions by redis. The most simple fix for me to implement would probably be this one out of all the alternatives below.The second alternative would be to volume map in your …