Pod fails to load due to issue creating the sqlite file

[patoarvizu]

Pod fails to load due to issue creating the sqlite file

[patoarvizu]

Hey @jadhad this sounds like an issue outside of the Helm chart itself, but let me see if I can help.

I see you're using a non-default StorageClass because the chart doesn't allow you to specify it, so that's something we can fix later, but can you tell me what plugin or provider that storage class uses? Does it require additional options/annotations to be set on the PersistentVolumeClaim object? I suspect that this might be an issue with the provisioning of the disk that's causing some permissions issues. The chart itself only creates the Kubernetes API objects, but I haven't tested it against Kubernetes 1.22, so it's possible that some modifications could be required.

Have you tried testing the setup locally following the steps under ./test-local/? You can modify the Makefile to tweak the parameters to k3d to pin it to a specific Kubernetes version.

[jadhad]

First of all - Great Job !!!

The idea to run these pods in kubernetes is much easier then editing the docker-compose files all the time.

As for you comments:

1. I changed the PersistentVolumeClaim chart a bit:

`apiVersion: v1
kind: PersistentVolumeClaim
metadata:
name: freqtrade-sqlite
spec:
accessModes:

• ReadWriteOnce
  resources:
  requests:
  storage: {{ .Values.bot.pvc_size }}

---

apiVersion: v1
kind: PersistentVolume
metadata:
name: freqtrade-pv
spec:
capacity:
storage: 1Gi
accessModes:

• ReadWriteOnce
  hostPath:
  path: /home/k8s-user/sqlite`

  but it still didn't help.

2. What version of Kubernetes you used to develop the chart?
3. I will try to use the 'test-local' and update.

Thank you very much!

[patoarvizu]

Did you add the PersistentVolume object yourself (either manually or on the chart)? The chart assumes that the storage class will automatically provision the PV given a PersistentVolumeClaim. If your storage class plugin requires manual steps, then it's likely this is a configuration issue on that side. Maybe the volume at that path (/home/k8s-user/sqlite) is being created with permissions such that it isn't accessible to the Docker daemon in the host?

I believe when I developed this chart I was using something like Kubernetes 1.18 or 1.19 if that helps.