How to skip database setup with Confluence Docker container

[Robin Jansohn]

I'm trying to clone a production instance of Confluence to our DEV environment using the official Confluence Docker Images.

We currently clone the DB schema to a new schema and copy the data directory to the DEV environment. We delete the confluence.cfg.xml file so docker will re-create it on the first start. However the template (https://bitbucket.org/atlassian-docker/docker-atlassian-confluence-server/src/master/config/confluence.cfg.xml.j2) currently hard-codes the setupStep to setupstart so we would always need to manually set-up the DB (this also fails by the way as the DB schema is not empty!).

I think the template file should be updated to allow skipping the DB setup and re-use an existing DB schema with existing data.

Have I missed something how to achieve this or is there currently no way to do this except manipulating the confluence.cfg.xml manually?

[James Wernicke]

I would also like this. An`ATL_SETUP_STEP=complete` flag that is used in the JInja template seems like it would suffice.