Skip to content
New issue

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

cannot run the container read-only #58

Open
francescou opened this issue Jul 26, 2017 · 2 comments
Open

cannot run the container read-only #58

francescou opened this issue Jul 26, 2017 · 2 comments

Comments

@francescou
Copy link

is there a way to run this image as read-only?

I run the container this way:

docker run --rm --name wildfly  \
  --read-only \
  --tmpfs /opt/jboss/wildfly/standalone/configuration/standalone_xml_history/  \
  --tmpfs /opt/jboss/wildfly/standalone/tmp/vfs/ \
  --tmpfs /opt/jboss/wildfly/standalone/data/ \
  --tmpfs /opt/jboss/wildfly/standalone/log/ \
  jboss/wildfly:10.1.0.Final

but I get the error WFLYDS0024: /opt/jboss/wildfly/standalone/deployments is not writable

the only workaround I've found is to mount /opt/jboss/wildfly/standalone/deployments/ as a volume.

@soufianebenali
Copy link

Hi @francescou,
after mounting /opt/jboss/wildfly/standalone/deployments/ as a volume I had an error also with the configuration files:

WFLYCTL0009: Failed to store configuration to standalone.xml: java.lang.IllegalStateException: java.lang.IllegalStateException: WFLYCTL0276: Failed to delete file /opt/jboss/wildfly/standalone/configuration/standalone.xml.tmp

Did you find any solution for this ad example disabling the configuration writing or something similar?
Thanks in advance

@voidengineer
Copy link

Did anyone solve this problem?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants