Open megian opened 3 years ago
I can't reproduce the bug with the bitnami image. It does work on my OpenShift 4 cluster.
Known good image SHA256s (tag 6.2.4
):
quay.io/bitnami/redis@sha256:838bb34507c5d786ac2e5e57cdb37239dd11ab75e49a595029e9af77a6f74378
quay.io/bitnami/redis@sha256:2c32c7577c8032f774f9dd22867a35a5fc9155b511ae07d20a6ccca6f16123e4
Could you please try again with one of those image SHAs?
I can reproduce the bug on rancher k8s. The special treatment for OCP masked the error.
The bitnami image only works with group 0
❯ ls -l /opt/bitnami/
drwxrwxr-x 1 root root 4096 Jun 1 16:39 redis
❯ docker run --user=1001:1001 -eALLOW_EMPTY_PASSWORD=yes -it quay.io/bitnami/redis:6.2.4
/bin/mkdir: cannot create directory '/opt/bitnami/redis/tmp': Permission denied
❯ docker run --user=1001:0 -eALLOW_EMPTY_PASSWORD=yes -it --rm quay.io/bitnami/redis:6.2.4
* Ready to accept connections
The component default suggest the usage of the Bitnami Redis image instead of the official one, but this doesn't work anymore with the component version v3.0.0.
We use internally the images:
Steps to Reproduce the Problem
Actual Behavior
Redis doesn't start, because the image doesn't match to the deployment configuration.
Expected Behavior
Either the Bitnami image support is going to be updated or the component defaults to the Docker Hub images.