Repository navigation
Running using readonly file system #47
Description
I am trying to run the container using readOnlyRootFilesystem set to true, and get the following error:
/docker-entrypoint.sh: 98: /docker-entrypoint.sh: cannot create /var/lib/jetty/jetty.start: Read-only file system
Is there a way to generate jetty.start somehow so I could still use readonly filesystem?
Reacted by n9
Activity
gregw commentedon Mar 21, 2021
you should be able to run the script
/generate-jetty-start.shfrom your Dockerfileomerlh commentedon Mar 21, 2021
Nice, this indeed helped - but now I am facing new Jetty issue - maybe you can help with that also? I am far from Jetty expert :)
lachlan-roberts commentedon Mar 23, 2021
You will still need a writeable temp directory for your WebAppContext.
The servlet spec says
lachlan-roberts commentedon Jul 26, 2021
This is an issue for the main jetty repository https://github.com/eclipse/jetty.project so feel free to reopen this there, but I think this could break a bunch of servlet features.
gregw commentedon Jul 26, 2021
@lachlan-roberts I actually think this would be a good feature to have. The need for a writable temp directory is part of the standard, but we have lots of non-standard modes of deployment.
It may need a change to core jetty to be disable the need for a writable temp dir.
@omerlh In the mean time, you could deploy using a context.xml file that creates a ServletContextHandler instead of a WebAppContext.