remove container_name?
For discussion: Removing the `container_name` lines lets us run many ckan-docker sites at the same time (assuming you use different ports) What is the benefit in forcing a container name in the docker compose config?
This commit is contained in:
parent
6bbc482e0d
commit
2a8f844ecf
@ -8,7 +8,6 @@ volumes:
|
||||
services:
|
||||
|
||||
ckan-dev:
|
||||
container_name: ${CKAN_CONTAINER_NAME}
|
||||
build:
|
||||
context: ckan/
|
||||
dockerfile: Dockerfile.dev
|
||||
@ -33,14 +32,12 @@ services:
|
||||
test: ["CMD", "wget", "-qO", "/dev/null", "http://localhost:5000"]
|
||||
|
||||
datapusher:
|
||||
container_name: ${DATAPUSHER_CONTAINER_NAME}
|
||||
image: ckan/ckan-base-datapusher:${DATAPUSHER_VERSION}
|
||||
restart: unless-stopped
|
||||
healthcheck:
|
||||
test: ["CMD", "wget", "-qO", "/dev/null", "http://localhost:8800"]
|
||||
|
||||
db:
|
||||
container_name: ${POSTGRESQL_CONTAINER_NAME}
|
||||
build:
|
||||
context: postgresql/
|
||||
environment:
|
||||
@ -60,7 +57,6 @@ services:
|
||||
test: ["CMD", "pg_isready", "-U", "${POSTGRES_USER}", "-d", "${POSTGRES_DB}"]
|
||||
|
||||
solr:
|
||||
container_name: ${SOLR_CONTAINER_NAME}
|
||||
image: ckan/ckan-solr:${SOLR_IMAGE_VERSION}
|
||||
volumes:
|
||||
- solr_data:/var/solr
|
||||
@ -69,7 +65,6 @@ services:
|
||||
test: ["CMD", "wget", "-qO", "/dev/null", "http://localhost:8983/solr/"]
|
||||
|
||||
redis:
|
||||
container_name: ${REDIS_CONTAINER_NAME}
|
||||
image: redis:${REDIS_VERSION}
|
||||
restart: unless-stopped
|
||||
healthcheck:
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user