I am Bob’s Co-Worker. We really appreciate all of the help on this issue.
We are attempting to deploy Docker containers to a test, QA, and production environments. These environments are running Docker Swam and backed by a private registry.
We currently build a Docker image based on the official Lucee 5.2 docker images, https://github.com/lucee/lucee-dockerfiles.
We are fully able to customize this image. We currently add custom certificates and custom jar files in addition to the application code.
Part of the image customization is a lucee-server.xml file that contains the data source connection parameters.
The image contains the test version of the lucee-server.xml. This works great and we are able to connect to launch our applications as expected.
As a best practice, we are reusing the container in QA but replacing the lucee-sever.xml with a QA version of the file. This replacement of the file is the problem. We insert the QA configuration using the docker configs functionality found in Docker Swarm. Docker swarm inserts the file as read-only, the file permissions are not configurable.
When we launch this container Lucee errors out with the following:
2017-12-18 17:16:46.57 lucee.runtime.exp.NativeException: /opt/lucee/server/lucee-server/context/lucee-server.xml (Read-only file system)
Our question is why does this file need to be read-write? Can we configure lucee to accept this file as read-only?