Skip to content
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

Bitnami Redis doesn't start up #24

Open
megian opened this issue Jul 29, 2021 · 2 comments
Open

Bitnami Redis doesn't start up #24

megian opened this issue Jul 29, 2021 · 2 comments
Labels
bug Something isn't working

Comments

@megian
Copy link
Contributor

megian commented Jul 29, 2021

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.

redis 13:13:51.94
redis 13:13:51.94 Welcome to the Bitnami redis container
redis 13:13:51.94 Subscribe to project updates by watching https://github.com/bitnami/bitnami-docker-redis
redis 13:13:51.95 Submit issues and feature requests at https://github.com/bitnami/bitnami-docker-redis/issues
redis 13:13:51.95
redis 13:13:51.95 INFO  ==> ** Starting Redis setup **
redis 13:13:51.96 WARN  ==> You set the environment variable ALLOW_EMPTY_PASSWORD=yes. For safety reasons, do not use this flag in a production environment.
redis 13:13:51.96 INFO  ==> Initializing Redis
*mkdir: cannot create directory '/opt/bitnami/redis/tmp': Permission denied*

We use internally the images:

  argocd:
    images:
      argocd:
        image: 'docker.io/argoproj/argocd'
      redis:
        image: 'docker.io/library/redis'
      kapitan:
        image: 'docker.io/projectsyn/kapitan'
      vault_agent:
        image: 'docker.io/library/vault'

Steps to Reproduce the Problem

  1. Deploy ArgoCD using the component v3.0.0 with the original image paths from the component

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.

@megian megian added the bug Something isn't working label Jul 29, 2021
@bastjan
Copy link
Contributor

bastjan commented Sep 7, 2021

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?

@bastjan
Copy link
Contributor

bastjan commented Sep 13, 2021

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

simu added a commit to projectsyn/getting-started-commodore-defaults that referenced this issue Nov 25, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants