hiimluck3r / h2m Goto Github PK

Describe the bug
A clear and concise description of what the bug is.

After redeployment using NextCloud Helm chart or recreating a pod, NextCloud can't access the user, provided in the configuration

starting nextcloud installation
The username is already being used
retrying install

Issue is also open in NextCloud's helm repo

To Reproduce
Steps to reproduce the behavior:

1. Redeploy nextcloud instance / kill and recreate nextcloud-web pod
2. Get error

Expected behavior
A clear and concise description of what you expected to happen.
Proceed without installation

Server (please complete the following information):

• OS: [e.g. iOS] Ubuntu Cloud-init 22.04
• Version of NextCloud helm chart: 4.6.2
• Version of k3s: v1.28.6+k3s2

Possible fix
Using install env in nextcloud entrypoint.sh set to false after the init installation.

if [ "$install" = true ]; then
                        run_path pre-installation

                        echo "Starting nextcloud installation"
                        max_retries=10
                        try=0

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is.
Deployments use too much resources (8GB RAM for 3-4 apps like nginx+apache+littlelink+ghost/nextcloud with caching)

Describe the solution you'd like
A clear and concise description of what you want to happen.
Limit deployments to not use too much resources.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Let it be as it is now.

Describe the bug
Title says all

To Reproduce
Steps to reproduce the behavior:
Install pterodactyl service to cluster

Expected behavior
Access pterodactyl panel