fix(docker): docker-compose-dev-essentials.yaml uses a different network when run standalone
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 7.2k
- Forks
- 718
- Avg merge
- 3d 1h
- Merged PRs (30d)
- 23
Description
Description
docker-compose-dev-essentials.yaml does not declare a network, while
docker-compose.yaml explicitly names its default network unstract-network.
As a result, running the essentials compose file standalone creates a
docker_default network:
docker compose -f docker-compose-dev-essentials.yaml up -d db
The same db service under the full compose configuration uses:
unstract-network
This is inconsistent with the networking configuration inside the essentials
file itself, where Traefik is explicitly configured with:
--providers.docker.network=unstract-network
Reproduction
From the docker/ directory:
docker compose -f docker-compose-dev-essentials.yaml up -d db
docker inspect unstract-db --format \
'NetworkMode={{.HostConfig.NetworkMode}} Networks={{json .NetworkSettings.Networks}}'
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in docker/docker-compose-dev-essentials.yaml and compare its network configuration with docker/docker-compose.yaml. Run the standalone db command from the issue, inspect unstract-db's networks, and confirm the essentials configuration uses unstract-network consistently with Traefik and the full compose setup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, docker-compose
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 88/100