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

Can't start Nextcloud because the version of the data (0.0.0.0) is higher than the docker image version () and downgrading is not supported. Are you sure you have pulled the newest image version? #569

Closed
gregory112 opened this issue May 9, 2024 · 1 comment
Labels
help wanted Extra attention is needed

Comments

@gregory112
Copy link

gregory112 commented May 9, 2024

Describe your Issue

CrashLoopBackOff on first install of Nextcloud helm. It's a new installation, why does this happen?

Logs and Errors

Can't start Nextcloud because the version of the data (0.0.0.0) is higher than the docker image version () and downgrading is not supported. Are you sure you have pulled the newest image version?

Describe your Environment

  • Kubernetes distribution: bare metal

  • Helm Version (or App that manages helm): 3.14.2, helmfile version 1.0.0-rc.0

  • Helm Chart Version: 4.6.8

  • values.yaml (my helmfile):

repositories:
  - name: nextcloud
    url: https://nextcloud.github.io/helm/

releases:
  - name: nextcloud2
    namespace: default
    chart: nextcloud/nextcloud
    values:
      - image:
          tag: 27.1.9
      - resources:
          requests:
            memory: "1024Mi"
            cpu: "2000m"
      - nextcloud:
          host: nextcloud.example.com
      - internalDatabase:
          enabled: false
      - externalDatabase:
          enabled: true
          type: mysql
          host: 192.168.1.12:3306
          database: nextcloud2
          user: nextcloud
          password: nextcloud
      - persistence:
          enabled: true
          storageClass: csi-rbd-sc
          size: 150Gi
      - ingress:
          enabled: true
          className: nginx
          tls:
            - hosts:
                - nextcloud.example.com
              secretName: nextcloud.example.com-cert
          annotations:
            cert-manager.io/cluster-issuer: letsencrypt
#            nginx.ingress.kubernetes.io/enable-cors: "true"
#            nginx.ingress.kubernetes.io/cors-allow-headers: "X-Forwarded-For"
            nginx.ingress.kubernetes.io/server-snippet: |-
              server_tokens off;
              proxy_hide_header X-Powered-By;
              rewrite ^/.well-known/webfinger /index.php/.well-known/webfinger last;
              rewrite ^/.well-known/nodeinfo /index.php/.well-known/nodeinfo last;
              rewrite ^/.well-known/host-meta /public.php?service=host-meta last;
              rewrite ^/.well-known/host-meta.json /public.php?service=host-meta-json;
              location = /.well-known/carddav {
                return 301 $scheme://$host/remote.php/dav;
              }
              location = /.well-known/caldav {
                return 301 $scheme://$host/remote.php/dav;
              }
              location = /robots.txt {
                allow all;
                log_not_found off;
                access_log off;
              }
              location ~ ^/(?:build|tests|config|lib|3rdparty|templates|data)/ {
                deny all;
              }
              location ~ ^/(?:autotest|occ|issue|indie|db_|console) {
                deny all;
              }
@jessebot jessebot added the help wanted Extra attention is needed label May 12, 2024
@gregory112
Copy link
Author

Seems that the nextcloud image was corrupted, where a lot of files has only 0 byte size, I pulled the same one again today and it works.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants