Pod fails to start when using dynamicPVC as workspace volume

DynamicPVC gets created and pod terminates.

Created Pod: kubernetes default/flutter-pvc-demo-29-sn3rd-s7ncc-xnm34

Still waiting to schedule task ‘flutter-pvc-demo-29-sn3rd-s7ncc-xnm34’ is offline

default/flutter-pvc-demo-29-sn3rd-s7ncc-xnm34 Container jnlp was terminated (Exit Code: 1, Reason: Error) - jnlp – terminated (1) -----Logs------------- Mar 15, 2023 3:32:01 AM hudson.remoting.jnlp.Main createEngine INFO: Setting up agent: flutter-pvc-demo-29-sn3rd-s7ncc-xnm34 Mar 15, 2023 3:32:01 AM hudson.remoting.Engine startEngine INFO: Using Remoting version: 3107.v665000b_51092 Exception in thread “main” java.io.IOException: The specified working directory should be fully accessible to the remoting executable (RWX): /home/jenkins/agent at org.jenkinsci.remoting.engine.WorkDirManager.verifyDirectory(WorkDirManager.java:249) at org.jenkinsci.remoting.engine.WorkDirManager.initializeWorkDir(WorkDirManager.java:201) at hudson.remoting.Engine.startEngine(Engine.java:309) at hudson.remoting.Engine.startEngine(Engine.java:285) at hudson.remoting.jnlp.Main.main(Main.java:276) at hudson.remoting.jnlp.Main._main(Main.java:271) at hudson.remoting.jnlp.Main.main(Main.java:237) [Pipeline] // node [Pipeline] } [Pipeline] // podTemplate [Pipeline] End of Pipeline Queue task was cancelled Finished: ABORTED

I don’t know what it means but that sounds like the problem. Maybe the volume is mounting with the wrong permissions? What does a dynamic volume do?