Skip to content

docker-compose setup unsuitable for multiple Skosmos deployments #1511

@namedgraph

Description

@namedgraph

Description of the problem

We want to deploy several Skosmos instances on the same machine, but the current docker-compose.yml has several issues that prevents this:

  • unnecessary container_name properties on services, which makes container names conflict when the second instance is started
  • docker-compose.yml file in a dockerfiles subfolder, which is used to construct container names (after explicit container_name are removed), e.g. dockerfiles_skosmos_1

My suggestion:

  • remove container_name properties
  • move docker-compose.yml to the top-level dir

Then we can launch Skosmos from 2 different folders, e.g. Skosmos-A and Skosmos-B, and the container names would become skosmos-a-skosmos-1, skosmos-a-virtuoso-1 etc. and skosmos-b-skosmos-1, skosmos-b-virtuoso-1, respectively. That way they will not conflict.

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions