trying into lucee on docker - nginx/apache and tomcat+lucee is inside a container, but the database - where it be? given I'm not developing another Twitter, can mysql be bundled within same image, so the app is deployed as one container?

but then you can't update your lucee image without taking down your database

right, because we don't update Lucee IN the container, but rather Lucee container, hmmm

then you can eventually get around to doing blue green deployments, leaving your database etc running and swapping your app server with updates

you can do a docker-compose file that then houses both your lucee and your database and possibly nginx or something else, and maybe even a fake mail server in separate containers in the same virtual docker network... but now if you are deploying to one of the major cloud providers i would use one of their hosted databases to host your database in production.. Just my opinion. and then everything lives nicely together... as a happy family.

Agree, detaching database to separate docker container or use hosted option seem like the only idea thinking ahead. I imagine also having application image, based on Lucee. Have Dockerfile created such a way that code is copied inside image, and then stored as Image, from which Containers are spinned