i am testing around with this Dockerimage: https://github.com/cybersonic/super-slim-lucee-docker/tree/main. In front i use a nginx reverse proxy (not dockerized). So far it rans very smooth but there is one problem. When i create some files trough lucee, the owner of the files is root(:root) (because of the container permissions). So there would be different options - the manual way would be to set permissions via cfexecute(“chmod”) after creating the files. But i am looking for something more fluent. I tried to run the whole Container with the ids of the site user…but his leads to different other problems inside the container. The best thing would tell lucee express to run as another user that root, but i have not found a way to do that. Maybe someone had did this before?

You can change the permissions as you like. I am using the lucee express startup script but you can add your own to run it as a different user and change the entrypoint

Thx @Mark Drew (he/him), i found the script and even checked catalina.sh but didn’t saw the way to define the user with which it will be started. Maybe you have another helpfull input?

At the end of the day you dont have to do specific users in docker a lot of the time

Yes…it would be fine if even the reverse proxy would be running in the container. But in my case its running native and the webroot is mapped into the container. So on every new created file the proxy couldn’t serve that static stuff because of the different permissions.

Oh I see... I try to separete those two out so that lucee doesnt even serve static stuff. That's up to an nginx container that redirects all requests for .cf* to the lucee container