-
Notifications
You must be signed in to change notification settings - Fork 57
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
Redis 7 #124
Comments
This should be covered by PR #146 |
Note that what Petr linked above will only cover c9s version of the image which will then be shipped to quay.io. Red Hat Container Images Catalog will get the image in some future version of RHEL9. |
C9S version is covered by this pull request. Including .devel-repo-rhel9 files also RHEL9 is tested. But it is not generally available yet. It will be available in future. |
Currently the README links to a fedora redis-7 image on quay.io, but the image is non existent at the moment. Is this an oversight? |
The image you mentioned exists in quay.io and I can access it just right. However it has different access settings than other our images - the repository seems to be set as private.. That could be the reason you can not access it. @phracek is there any reason for quay.io/fedora/redis-7 being private repository? |
it was typo. |
I've set the repo to public. The image should be accesible for everyone now. Thanks @AlexStorm1313 for notifying us. |
Thank you! @zmiklank |
@AlexStorm1313 redis-7 is available on quay.io. @anludke Does it make sense to close this issue in case it is already available on quay.io based on fedora base image? Currently we do not have any timeline, when the image will be available in Red Hat Container catalog. |
@AlexStorm1313 @anludke . redis-7 is now available in Red Hat Container catalog. Can we close this issues? |
Excuse me for the late reply @phracek, setting the quay.io repo to public solves it for me. |
Hi there,
Is there a plan and timeline to publish Redis 7 in Red Hat Container Images Catalog?
Thank you.
The text was updated successfully, but these errors were encountered: