Running using readonly file system

[omerlh]

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?

[gregw]

you should be able to run the script /generate-jetty-start.sh from your Dockerfile

[omerlh]

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 :)

Parent for temp dir not configured correctly

[lachlan-roberts]

You will still need a writeable temp directory for your WebAppContext.

The servlet spec says

A temporary storage directory is required for each servlet context. Servlet containers
must provide a private temporary directory for each servlet context, and make it
available via the javax.servlet.context.tempdir context attribute.

[lachlan-roberts]

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]

@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.