nextcloud / nextcloud/helm

File CAN_INSTALL is missing from your config directory.

Open
#628 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

needs info
Dominant language
Go Template
Stars
534
Forks
314
Avg merge
42m
Merged PRs (30d)
1

Description

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.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the supplied values.yaml and the Helm chart's persistence, config, and externalDatabase settings for chart version 5.5.6. Check the Nextcloud pod behavior and confirm when the external PostgreSQL database is seeded relative to deployment. Done means a clean installation completes without the CAN_INSTALL error.

Written by the indexing model from the issue text.

Assessment

Tech stack
helm, kubernetes, postgresql
Domain
databases, devops, infrastructure
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.