From 34f15a071a9df12986654593193235a21a774fc8 Mon Sep 17 00:00:00 2001 From: Trevor Bramwell Date: Wed, 26 Jul 2017 11:22:54 -0700 Subject: Mount PostgreSQL Data from Persistent Volume Each time the postgresql container is torn down the database is lost. By using a presistent volume managed outside of docker compose, the postgresql data can persist across updates and service restarts. The volume needs to exist before the postgres container can start: this is done with the 'make data' command. Note: postgres container creates a volume at /var/lib/postgresql/data. Mounting at this location ensures the data is persisted into the external volume. Change-Id: I958ba57fc735c594378d575bc7108bee0d30c1e3 Signed-off-by: Trevor Bramwell --- tools/pharos-dashboard/docker-compose.yml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) (limited to 'tools/pharos-dashboard/docker-compose.yml') diff --git a/tools/pharos-dashboard/docker-compose.yml b/tools/pharos-dashboard/docker-compose.yml index 16b8c0fd..44a263f0 100644 --- a/tools/pharos-dashboard/docker-compose.yml +++ b/tools/pharos-dashboard/docker-compose.yml @@ -50,7 +50,7 @@ services: env_file: config.env volumes: - ./config/postgres/docker-entrypoint-initdb.d:/docker-entrypoint-initdb.d - - /var/lib/pharos_dashboard/postgresql:/var/lib/postgresql + - pharos-data:/var/lib/postgresql/data rabbitmq: restart: always @@ -72,3 +72,6 @@ services: - rabbitmq volumes: - ./:/pharos_dashboard +volumes: + pharos-data: + external: true -- cgit 1.2.3-korg