docker compose?

[hiro5id]

One of the biggest reasons I want to keep my containers as docker-compose is for easy and quick redundency in case of emergency. For example if in a pinch, i have to start up my services on a spare computer, I don't have to worry about TrueNAS, i can simply clone my infastructure-as-code git repo onto a new machine that has docker installed, and run two docker commands and i'm up and running again.

 

[truecharts]

@Ixian

Name: pvc-fad093e4-4a9d-4916-9852-13485e1b7f30
Labels: <none>
Annotations: pv.kubernetes.io/provisioned-by: zfs.csi.openebs.io
Finalizers: [kubernetes.io/pv-protection]
StorageClass: ix-storage-class-esphome
Status: Bound
Claim: ix-esphome/esphome-config
Reclaim Policy: Retain
Access Modes: RWO
VolumeMode: Filesystem
Capacity: 999Gi
Node Affinity:
Required Terms:
Term 0: openebs.io/nodeid in [ix-truenas]
Message:
Source:
Type: CSI (a Container Storage Interface (CSI) volume source)
Driver: zfs.csi.openebs.io
FSType: zfs
VolumeHandle: pvc-fad093e4-4a9d-4916-9852-13485e1b7f30
ReadOnly: false
VolumeAttributes: openebs.io/cas-type=localpv-zfs
openebs.io/poolname=apps/ix-applications/releases/esphome/volumes
storage.kubernetes.io/csiProvisionerIdentity=1654201089570-8081-zfs.csi.openebs.io

according to this information the PVC folder of the /config mount is in the /ix-applications/releases/esphome/volumes folder, when I look there there is nothing but another folder. Any ideas?

PVC's are not accessable on the host filesystem.
You will need TrueTool or manuall tricks.
in both of those cases you cannot(!) have the App running with PVCs accessable from the host filesystem in any way, shape or form. PVC is simply not designed to be the same as hostPath storage.

 

[Jip-Hop]

There's now a new, experimental, way to run docker-compose on SCALE without relying on k3s: running persistent 'jails' with systemd-nspawn.