[Feature Request] Disable built-in DB and use external DB, possible?

[BloodyIron]

Having the database built-in to the image is pretty nice, but since I want to probably run this in my kubernetes cluster, I really would like the option (via environment variables? unsure) to disable the built-in database in the image, and feed it database connection info to connect to database services external to the image.

This is me requesting this feature be added to all images (not just latest Concrete CMS version). Could we get that please?

[mlocati]

Docker5 images are meant to offer an easy and quick way to test and run Concrete with a single CLI command.
If you need a more complex (and complete?) setup, I'd avoid docker5 and use the docker PHP fpm images to install concrete from scratch.

[BloodyIron]

Docker5 images are meant to offer an easy and quick way to test and run Concrete with a single CLI command. If you need a more complex (and complete?) setup, I'd avoid docker5 and use the docker PHP fpm images to install concrete from scratch.

Why is that preferable over what I'm asking? To me there's appeal in Concrete CMS being delivered as a docker image for upgrading... am I not accounting for something?

[mlocati]

The only problem I see is lack of time to provide support for it.