This message was deleted.

Solved. Dumb problem.

What was the fix please? I'm receiving the same error but on a K8's Cluster

@microscopic-easter-64692 it was embarrassingly dumb. DiskPressure taint on the k3s node it spins up in docker was preventing pod scheduling. I had it in my mind that there was no way the DiskPressure taint was valid so I just kept on as if it wasn’t telling me exactly what the problem was.

Ahhh I see, I've been using helm to provision.. so will output the deployment to a yaml file and see whether there is any issues with the specs! Thanks 🙂