Comments (8)
Same issue here. Connecting applications complain about "Redis is running in protected mode". This was not an issue before the updates (was using "latest" tag). Now, since all the images available in docker hub are updated, there isn't an option to go back to a previously working version either.
from docker-redis-cluster.
@lreher @Sedemicra grokzen/redis-cluster:latest
tag was updated yesterday from 6.2 to 7.0 and in that build the default is protected mode see #153 for it. You will have to disable protected mode manually in 7.0 and above before running the cluster.
The best for you todo is to use the old 6.2.x tags if you really depend on it. Running on :latest
in the docker world is like running directly from master
branch in a coding project, it is where anything and everything can break so it is risky to run on it. Change the tags on your end back one major version and you should be good to go again
from docker-redis-cluster.
Well aware of the risks of :latest
, just taking over someone elses project :)
Just before my previous comment I didn't see the 6.2.x tags in docker hub so I figured they were no longer an option, but now they are available again - not sure what happened there. But thanks for making me look again @Grokzen
Might consider trying some option from #149 in the future, but currently 6.2.x tag will work just fine.
from docker-redis-cluster.
All tags for 6.0, 6.2 & 7.0 should have been there since the last year at least O.o i hope so at least, most of the time i don't keep up with minor versions as they release. I have been thinking about some other solutions for that, maybe make a cron based solution with a github action that constantly builds all released versions for example, but that solution is not ready yet.
On the config side i have also been messing around with a new configuration solution that uses and makes environment variables much more usefull and able to configure anything instead of having to implement and support each key and variable as they are needed. The simplest way is to just volume map in your own configuration files to make it what you want, but i think that environment variables is the way to really go in the long run as things is going towards env vars more.
from docker-redis-cluster.
Thanks for the follow up, we've just replaced the image with an older digest.
from docker-redis-cluster.
I saw the same issue as @Sedemicra, all the tags look like they were replaced yesterday?
from docker-redis-cluster.
It seems there is a bug in docker hub tags page logic.
When I open (or refresh) it I only see "latest" and 7.0.x tags on first page, and on next page there are only 6.0.x tags. I only see 6.2.x tags when I navigate back to first page and then they miraculously appear. This is why I originally missed them.
It seems to be some kind of general issue in docker hub as I see similar problem on other projects.
from docker-redis-cluster.
@Sedemicra I think it is based on what order i upload the latest layers in, best is to sort them Z-A then it would always come in the correct order
from docker-redis-cluster.
Related Issues (20)
- PUBLIC NOTICE: Splitting cluster and sentinel into two separate docker images
- Rewrite travis-ci into github actions
- Old docker hub tags missing over night? HOT 1
- redis 'ready' event is not triggered HOT 3
- how to set every node password HOT 1
- redis.tmpl is missing
- Delete redis data after make down HOT 1
- Image for Apple M1 docker HOT 4
- Can I run a Redis cluster without a ".conf "configuration file like Mariadb Galera and just configure it all in the docker-comemater.yml file? HOT 1
- Cannot redirect when connecting from remote HOT 3
- Wrong redis version used HOT 3
- Images before < 6.x have been dropped from registry HOT 1
- Podman not supported HOT 5
- Image with tag `latest` not latest HOT 1
- Version 7+ cannot handle non-localhost connections as protected mode is on and authentication is not supported HOT 8
- Always more than 10 sec to "down" the container HOT 2
- Docker image with "latest" tag is not actually latest HOT 2
- Error when using jedis and test container for java HOT 1
- multiple critical CVEs in the image HOT 4
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from docker-redis-cluster.