Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Support of networks in Compose.yml

Open
#2 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
docker-compose, rust
Domain
devops, networking

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.

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.

Dominant language
Rust
Stars
2k
Forks
58
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from lapce/lapdev

All issues in lapce/lapdev

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.