conjur-quickstart README.md instructs to delete the data directory once establishing persistence. Why?

Hello all, my first post. :slight_smile:
I set up a Conjur OSS instance using conjur_quickstart. All went well with the setup. I further decided to make the database persistent using the instructions contained in the associated README.md.

That also worked. I can now start/stop my VMware player based conjur instance, store secrets, retrieve secrets and have those secrets persist between docker compose down / up operations.

There is one thing that puzzles me in the instructions. After one goes through all the steps of setting up an instance for persistence (creating a data directory, updating the docker-compose.yml file, compose down/up, and reassociating the client with the server), the very next set of instructions says to delete the data directory you created in step 1. This step I have not done.

Unless I’m missing something (quite possible), this doesn’t make sense to me. If you delete the data directory you created (i.e. temp-db-data), I expect you’ve now destroyed your data. Is this not where the data is persisting when you bring your Conjur related containers down?

What am I missing?

Here is the snippet of instruction I’m referencing. Its the last step after you’ve established persistence.

Delete the Conjur data directory when done

For added security, remember to delete the data directory that you created
in Step 1 of the
Set up a Conjur Open Source environment with persistence
section above.

Hi @jack21,

My understanding is that the suggestion to delete the directory containing the persisted database is meant for after you’ve finished experimenting and are all done with the environment. You are correct that deleting it will destroy the data you just persisted. This setup with Docker Compose is not a production-ready strategy for deploying Conjur so it’s assumed that after trying it out, you’ll want to delete the environment.

Please let me know if you have any other questions or concerns.
Shlomo