[BUG] 500 on items/create

[Gisleburt]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

When arriving on a fresh, the homescreen works fine, but clicking 'Add an application here' causes a 500

Expected Behavior

I should be able to add an application

Steps To Reproduce

I am trying to run the container in kubernetes (see below for deployment yaml).

I have tried both 2.5.6 and 2.5.5 (based on a similar sounding bug in linuxserver/Heimdall#1183)

I've also tried with and without the PUID and PGID but its the same either way (also other files have been written to the volume)

Logs:

• no errors in kubectl logs ...
• there is no error log file in /config/log/heimdall
• /config/log/nginx/error.log exists but is empty
• /config/log/nginx/access.log shows the 500s but has no useful info about them
• /config/log/php/error.log only says fpm is ready

Some possible quirks:

• I'm using an NFS persistent volume however
  • other files have been created perfectly fine
  • 1Gi is assigned but only ~296K is being used
• I'm doing edge TLS decryption handled by cert manager, internal traffic is on 80

With no logs I'm not sure what to go off

Environment

- OS: This... needs some explaining

I'm running a multi arch k3s cluster across several NUCs (amd64) running latest Ubuntu LTS and Pi4's (arm64) running latest Raspbian

_Currently_ the service is running on the NUCs so the architecture is amd64, however, I haven't specified that it needs to run there so it could change.

- How docker service was installed:

k3s using custom Ansible, though this is the only app I've struggled with like this

If you're super curious, its here though some of the README is a bit out of date: https://github.com/gisleburt/homelab

CPU architecture

x86-64

Docker creation

---
kind: Deployment
apiVersion: apps/v1
metadata:
  labels:
    app: heimdall
  name: heimdall
  namespace: heimdall
spec:
  replicas: 1
  selector:
    matchLabels:
      app: heimdall
  template:
    metadata:
      labels:
        app: heimdall
    spec:
      containers:
        - name: heimdall
          image: linuxserver/heimdall:2.5.6
          imagePullPolicy: Always
          ports:
            - name: heimdall
              containerPort: 80
          env:
            - name: TZ
              value: Europe/London
            - name: PUID
              value: "1000"
            - name: PGID
              value: "1000"
          volumeMounts:
            - name: config
              mountPath: "/config"
      volumes:
        - name: config
          persistentVolumeClaim:
            claimName: config

Container logs

[migrations] started
[migrations] 01-nginx-site-confs-default: skipped
[migrations] 02-default-location: skipped
[migrations] done
───────────────────────────────────────

      ██╗     ███████╗██╗ ██████╗ 
      ██║     ██╔════╝██║██╔═══██╗
      ██║     ███████╗██║██║   ██║
      ██║     ╚════██║██║██║   ██║      
      ███████╗███████║██║╚██████╔╝
      ╚══════╝╚══════╝╚═╝ ╚═════╝ 

   Brought to you by linuxserver.io
───────────────────────────────────────

To support LSIO projects visit:
https://www.linuxserver.io/donate/

───────────────────────────────────────
GID/UID
───────────────────────────────────────

User UID:    1000
User GID:    1000
───────────────────────────────────────

using keys found in /config/keys
New container detected, installing Heimdall
[custom-init] No custom files found, skipping...
[ls.io-init] done.

[github-actions]

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

[Dapolux]

Hi @Gisleburt,
I have the same problem on my side, the only way i found to solve it, is having my docker LXC CT as an "Unprivilegied CT".

[aptalca]

To clarify, we do not support docker in lxc. Even the proxmox (majority of lxc users seem to be proxmox users based on the issue reports we get) devs recommend against running docker in lxc. So that wouldn't be considered a solution.

For the OP, your issue is likely due to storing the config folder on nfs. We don't support or recommend putting config folders on a remote share (media/data folders are fine). Especially databases do not like that. On k8s, you can either do local or block storage like longhorn.

[Gisleburt]

Thanks for the response @aptalca. I'd been wanting to add Longhorn for a little while so this was a nice excuse, wish I'd done it earlier now, it was far easier than my NFS provisioner 😛 .

Unfortunately I still get a 500 and still don't get anything in the logs.

[Dapolux]

To clarify, we do not support docker in lxc. Even the proxmox (majority of lxc users seem to be proxmox users based on the issue reports we get) devs recommend against running docker in lxc. So that wouldn't be considered a solution.

For the OP, your issue is likely due to storing the config folder on nfs. We don't support or recommend putting config folders on a remote share (media/data folders are fine). Especially databases do not like that. On k8s, you can either do local or block storage like longhorn.

Thanks for the information.

By the way, doing additional tests, even if it's not a recommended solution to use LXC docker, switching from a CT template "turnkey" to a CT template "standard" is solving the issue on my landscape.
All is working fine on my side now.

[LinuxServer-CI]

This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.

[Gisleburt]

What else can I add to help?

[j0nnymoe]

Your issues are probably just because of using k3s. While I've seen users say they have it working, it's not a platform we provide support for.

[Gisleburt]

Ok, I'll try something else. Thanks for looking into it.

[github-actions]

This issue is locked due to inactivity