We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I tried to get plantuml/plantuml-server:jetty running on OpenShift, and go the following error:
plantuml/plantuml-server:jetty
/docker-entrypoint.sh: 98: /docker-entrypoint.sh: cannot create /var/lib/jetty/jetty.start: Read-only file system
The same error can be reproduced by running docker with --read-only option:
--read-only
docker run -p 8080:8080 --read-only plantuml/plantuml-server:jetty
I've found this jetty issue which gave me the hint to get things working:
First step was to build a new image:
FROM plantuml/plantuml-server:jetty RUN /generate-jetty-start.sh
docker build -t plantuml/plantuml-server:jetty-readonly .
And then run it with
docker run -p 8080:8080 --read-only -v /tmp/jetty plantuml/plantuml-server:jetty-readonly
Would you consider include RUN /generate-jetty-start.sh in your Dockerfile.jetty and some documentation on how to run this in read-only mode?
RUN /generate-jetty-start.sh
Dockerfile.jetty
The text was updated successfully, but these errors were encountered:
Yes, of course. The easiest way would de that you submit a merge request for that.
Thanks!
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
I tried to get
plantuml/plantuml-server:jetty
running on OpenShift, and go the following error:The same error can be reproduced by running docker with
--read-only
option:I've found this jetty issue which gave me the hint to get things working:
First step was to build a new image:
And then run it with
Would you consider include
RUN /generate-jetty-start.sh
in yourDockerfile.jetty
and some documentation on how to run this in read-only mode?The text was updated successfully, but these errors were encountered: