# How to utilize Containerized Jenkins Inbound Agent with Read-Only Root Filesystem?

**URL:** <https://community.jenkins.io/t/how-to-utilize-containerized-jenkins-inbound-agent-with-read-only-root-filesystem/3438>\
**Category:** Ask a question\
**Created:** [August 19, 2022, 5:15pm UTC](https://community.jenkins.io/t/how-to-utilize-containerized-jenkins-inbound-agent-with-read-only-root-filesystem/3438 "2022-08-19T17:15:21Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![jakauppila](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/jakauppila/32/314_2.png) [@jakauppila](https://community.jenkins.io/u/jakauppila)\
**Post date:** [August 19, 2022, 5:15pm UTC](https://community.jenkins.io/t/how-to-utilize-containerized-jenkins-inbound-agent-with-read-only-root-filesystem/3438/1 "2022-08-19T17:15:21Z")

</div>

We are in the process of standing up a Serverless Jenkins on AWS Fargate as described in this blog post [Building a serverless Jenkins environment on AWS Fargate | AWS DevOps Blog](https://aws.amazon.com/blogs/devops/building-a-serverless-jenkins-environment-on-aws-fargate/)

So far things are going well, but one requirement we have is that we run our containers with a read-only root file system and thus need to add the appropriate volumes to those folders that need write access.

Is there a list of required directories that must be writable within the inbound agent image? [GitHub - jenkinsci/docker-inbound-agent: Docker image for a Jenkins agent which can connect to Jenkins using TCP or Websocket protocols](https://github.com/jenkinsci/docker-inbound-agent)

I’ve tried explicitly setting the `JENKINS_AGENT_WORKDIR` and creating a volume

```auto
ENV JENKINS_AGENT_WORKDIR=/home/jenkins/workspace
VOLUME ["/home/jenkins/workspace"]

```

but am met with a handful of errors including:

`WARNING: No Working Directory. Using the legacy JAR Cache location: /home/jenkins/.jenkins/cache/jars`