[ https://issues.jboss.org/browse/WFCORE-4135?page=com.atlassian.jira.plugi... ] Rafael Ruiz commented on WFCORE-4135: ------------------------------------- I have found twice problems using software based on wildfly-core (EAP, but also Infinispan/Datagrid) when running in a containerized environment. For example because of customized installations $WFCORE/standalone/configuration had to be read-only. Even running on non-containerized environment, but with very strict security rules that forced that directory to be only for read. Also, in a less technical way, I heard some critics of users saying this is a 'legacy behaviour' senseless in containers. Maybe I have too much contact with cloud-native people. ;-) "_Writing to history is required when --read-only-server-config=<config> is set if any management op that would require reload is invoked. The backup is what's read when 'reload' is invoked. If history backups were disabled the server would have to properly account for this use case; e.g. by failing any such op_" I have tested to reload from CLI and its seems to work, but with no real changes pending of reload. Will do more tests -- This message was sent by Atlassian JIRA (v7.5.0#75005)