Support of networks in Compose.yml
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 2k
- Forks
- 58
- PR merge metrics
- No merged PRs in 30d
Description
https://www.architect.io/blog/2023-03-23/manage-networking-with-docker-compose/
Docker Compose supports multiple networks, and you can define your services to belong to which networks.
Currently Lapdev only creates one shared network and adds all containers to the same network. And we'll need to create multiple networks according to the network configs in compose.yml and only allow services to networks as defined in compose.yml.
Contributor guide
No contributing guide indexed for this repository
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 by tracing how Lapdev currently creates its single shared network, then compare that behavior with the network definitions and service memberships in compose.yml. Use the Docker Compose networking reference linked in the issue to identify the expected configuration, and consider the work complete when services are attached only to the networks declared for them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker-compose, rust
- Domain
- devops, networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100