there was an issue where https://git.dotya.ml/dotya.ml/homepage
containers were getting orphaned when this project was deployed.
messages like the following were printed:
Removing orphan container "src_homepage_2"
Removing orphan container "src_homepage_4"
Removing orphan container "src_reverse-proxy_1"
Removing orphan container "src_homepage_3"
Removing orphan container "src_homepage_1"
The author of the accepted answer of a related SO thread links to
docker-compose documentation, explaining how setting a project variable
should resolve this.
the COMPOSE_PROJECT_NAME environment variable is likely the same for
both projects in question here (homepage and docs) as they're both being
deployed by drone from the /drone/src directory, which is also set by
drone as the WORKDIR). basename - here src - is used as the project name
if not specified otherwise.
to conclude, running both [compose deployments] with a unique project
name should fix the issue.
refs:
https://stackoverflow.com/a/59173539https://docs.docker.com/compose/reference/overview/#use--p-to-specify-a-project-namehttps://docs.docker.com/compose/reference/envvars/#compose_project_namefix#1
docs image is built JIT from Dockerfile.
the logic for the compose file is based on the one used in
https://git.dotya.ml/dotya.ml/homepage yet the traefik part was not
used.
surtur