# Trying to execute jnlp-inbound in in-house Kubernetes cluster, but it keeps in ContainerCreating, due to MountVolume.SetUp... no space left on device

**URL:** <https://community.jenkins.io/t/trying-to-execute-jnlp-inbound-in-in-house-kubernetes-cluster-but-it-keeps-in-containercreating-due-to-mountvolume-setup-no-space-left-on-device/9729>\
**Category:** Using Jenkins\
**Tags:** question, kubernetes\
**Created:** [September 21, 2023, 12:49pm UTC](https://community.jenkins.io/t/trying-to-execute-jnlp-inbound-in-in-house-kubernetes-cluster-but-it-keeps-in-containercreating-due-to-mountvolume-setup-no-space-left-on-device/9729 "2023-09-21T12:49:36Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![jonbrohauge](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/jonbrohauge/32/103_2.png) [@jonbrohauge](https://community.jenkins.io/u/jonbrohauge)\
**Post date:** [September 21, 2023, 12:49pm UTC](https://community.jenkins.io/t/trying-to-execute-jnlp-inbound-in-in-house-kubernetes-cluster-but-it-keeps-in-containercreating-due-to-mountvolume-setup-no-space-left-on-device/9729/1 "2023-09-21T12:49:36Z")

</div>

Hi all,

I’m trying to get my head wrapped around using the Kubernetes Plugin to deploy agents on a local Kubernetes cluster, but I never can get past the jnlp-container having a State: Waiting → Reason: ContainerCreating

The event log keeps telling me that a mount failed.

 ![image](https://europe1.discourse-cdn.com/flex013/uploads/jenkins/original/2X/2/2661d05e4a141819004025effcfb54a838807a15.png)  
 ![image](https://europe1.discourse-cdn.com/flex013/uploads/jenkins/original/2X/e/e7ab5a8d1d66c439cbe6b679be8f477fd3512b33.png)

I have verified that I am indeed not short of available space.  
Cleaning up, using `docker system prune --all --force` does not help

I am running this on a vanilla kubernetes setup v 1.28.2. The Jenkins instance I am trying to execute the jobs on, is running on the cluster, and has no issue accessing the volumes.

I am using Jenkins v.2.423  
The (currently) latest in all plugins

 ![image](https://europe1.discourse-cdn.com/flex013/uploads/jenkins/original/2X/2/2135e406aa493473155a3f01a995223b45fa213f.png)

How do I debug this issue?

---

<div class="post-metadata">

**Author:** ![doofus\_canadensis](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/doofus_canadensis/32/771_2.png) [@doofus\_canadensis](https://community.jenkins.io/u/doofus_canadensis)\
**Post date:** [September 21, 2023, 1:53pm UTC](https://community.jenkins.io/t/trying-to-execute-jnlp-inbound-in-in-house-kubernetes-cluster-but-it-keeps-in-containercreating-due-to-mountvolume-setup-no-space-left-on-device/9729/2 "2023-09-21T13:53:36Z")

</div>

Are you certain that kubernetes is using docker as its backend? If it is not, then pruning docker is not going to have any effect on disk space.

---

<div class="post-metadata">

**Author:** ![jonbrohauge](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/jonbrohauge/32/103_2.png) [@jonbrohauge](https://community.jenkins.io/u/jonbrohauge)\
**Post date:** [September 22, 2023, 5:27am UTC](https://community.jenkins.io/t/trying-to-execute-jnlp-inbound-in-in-house-kubernetes-cluster-but-it-keeps-in-containercreating-due-to-mountvolume-setup-no-space-left-on-device/9729/3 "2023-09-22T05:27:40Z")

</div>

I am quite certain I am using docker.  
Executing `docker ps` on any node, shows  
The containers running kubernetes “stuff” as expected.