I think you need to store the config is out of doc...
# lucee
m
I think you need to store the config is out of docker than make a mapping for that config. If not when you restart the docker everything is gone
f
Hi, indeed, after restarting docker, all my config is gone. But the strange thing is: just sometimes (which is a behaviour, I never saw when using Docker). What I'm doing is: I have stored most of my config in my repo and in Dockerfile I'm using COPY commands to copy lucee-web.xml.cfm, scheduler/scheduler.xml and other files over into the container to the /opt/lucee/web directories. It used to work for months properly but a few weeks ago it started to become unstable somehow and I don't have the slightest idea what caused that. Any hints what is causing the config path to change (and where this path is actually set, so I could force the path to be set correctly)? Thanks a lot, Cheers
p
Can you share your Docker file?
f
Hi @Patrick, sure, here it is. Thanks!
Also, here's the corresponding docker-compose.yml snipped (note: args and environment is collapsed for better readability). Cheers
m
message has been deleted
That is the mapping between you real folder vs docker folder
As the picture said : your lucee is in /opt/lucee
f
Yes that's clear. The issue is that after restarting, Lucee thinks that the web context moved from /opt/lucee/web to /var/www/opt/lucee/web which is not understandable to me...
m
Let's me check more the docker file
or should i send you an example then you can found by your selft
message has been deleted
the scheduler is gone
please check this script for schedule
message has been deleted
something wrong here
And you can going side the docker to check the output
with the command like this
If hurry I can ask an Devops guy to support you
f
Thanks, I'm just removing (on build time) the default scheduler.xml file and then putting it together using several artifacts from my docker config files. So, the file is there (and if I login to the docker container, file is there and valid). The issue is that lucee is looking in a different folder. Also mail settings, and other settings are lost with that. Lucee thinks, everything is located in /var/www/opt/lucee/web/ folder.
m
first go inside the docker to make sure the file and location is correct
f
Files looks fine: But it is not taken into consideration, as the web context configuration file is again prefixed with /var/www
m
maybe you need to add a command to copy to correct folder
then you got what you need
f
I AM copying to the right folder ( /opt/lucee/web ). The issue is that lucee forgets this default path over time and starts thinking that the path is /var/www/opt/lucee/web ). And I cannot find out what is triggering this behaviour or where I can configure the right path /opt/lucee/web somewhere so that it is fixed and not "dynamically".