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

File CAN_INSTALL is missing from your config directory. #628

Open
Jymitar opened this issue Sep 14, 2024 · 1 comment
Open

File CAN_INSTALL is missing from your config directory. #628

Jymitar opened this issue Sep 14, 2024 · 1 comment
Labels
needs info Not enough information provided

Comments

@Jymitar
Copy link

Jymitar commented Sep 14, 2024

Describe your Issue

I have setup a clean k3s cluster and I am trying to install NextCloud but for some reason it doesn't work.
I am using the latest HELM chart version.

Logs and Errors

Nextcloud
Error
It looks like you are trying to reinstall your Nextcloud. However the file CAN_INSTALL is missing from your config directory. Please create the file CAN_INSTALL in your config folder to continue.

Nextcloud – a safe home for all your data

Describe your Environment

  • Kubernetes distribution: k3s - 1.30.4

  • Helm Version (or App that manages helm): v3.12.3 using FluxCD 2.3.0

  • Helm Chart Version: 5.5.6

  • values.yaml:

  values:
    replicaCount: 1
    phpClientHttpsFix:
      enabled: true
      protocol: https
    nextcloud:
      host: cloud.example.com
      existingSecret: 
        enabled: true
        secretName: nextcloud-cred
      configs:
        custom.config.php: |-
          <?php
          $CONFIG = array (
            'maintenance_window_start' => 1,
            'default_phone_region' => 'BG',
            'default_timezone' => 'Europe/Sofia',
            'overwriteprotocol' => 'https',
            'overwritehost' => 'cloud.example.com',
            'trusted_proxies'   => ['10.0.0.0/8'],
          );
      phpConfigs:
        opcache-recommended.ini: |
          opcache.enable=1
          opcache.interned_strings_buffer=32
          opcache.max_accelerated_files=30000
          opcache.memory_consumption=512
          opcache.save_comments=1
          opcache.revalidate_freq=60
          opcache.jit=1255
          opcache.jit_buffer_size=128M
    persistence:
      enabled: true
      existingClaim: nextcloud
      nextcloudData:
        enabled: true
        existingClaim: nextcloud-data
    cronjob:
      enabled: true
    internalDatabase:
      enabled: false
    externalDatabase:
      enabled: true
      type: postgresql
      existingSecret:
        enabled: true
        secretName: nextcloud-postgres-nextcloud-admin
        usernameKey: LOGIN
        passwordKey: PASSWORD
        hostKey: HOST
        databaseKey: DATABASE_NAME

Additional context, if any

I am using local-path to provision the volumes
I am using a secret to pass the initial username and password.
I am using an already provisioned PostgreSQL instance using the bitnami chart - 15.5.31
I am using external postgres operator to create the database the user credentials and the secret I pass as an existing secret.
All secrets values are passed correctly to the pod. The database is being seeded after nextcloud is deployed. There are no error logs in the pod. When I git the domain I get the above error.

Any advice would be appreciated.

@jessebot
Copy link
Collaborator

Since this is a new install and can you try deleting the install, and then wiping/deleting the PVC entirely and trying again? This typically happens when there's already data in the PVC. If your install takes a little bit, you may also want to adjust the probes, but this may not be necessary. You can learn more about probes here: https:/nextcloud/helm/tree/main/charts/nextcloud#probes-configurations

@jessebot jessebot added the needs info Not enough information provided label Sep 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs info Not enough information provided
Projects
None yet
Development

No branches or pull requests

2 participants