2
2
I have recently started to experiment with Docker and when it comes to code deployments (i.e. node server) it works extremely well. However when it comes to deployment of a couchDB server it poses a challenge. The challenging aspect is probably related to my ignorance on the topic.
The current setup: Continuous deployment to AWS EC2 instance
The Issue: Every deployment wipes the database and reinstalls couchDB
End goal: Deployments should not remove and reinstall the database. They should simply update the couchdb configuration if one is provided (i.e. turn off admin party mode, add user, ...)
Dockerfile:
Pretty simple: FROM couchdb:latest
What are some approaches I can use to accomplish this?
The more I think about it I am not entirely sure I should be using Docker for database deployment. Rather, I should use it as a one-time-setup. – dipole_moment – 2016-07-17T04:26:34.233
Hey if you check @werty1st's response you can see that deploying configured CouchDB instances is supported so long as you use a separate container for persistent data or write the data to a host directory outside the container. – Ilias Karim – 2018-08-09T04:00:25.463