Feature: Isolate Containers by Project
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 37.4k
- Forks
- 3k
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 73
Description
I'd like to express my gratitude for this awesome open-source project. ❤️
The concept and workflow are truly impressive.
I'd like to propose an option to create network configurations based on projects.
This would enable isolation between containers from different projects, preventing access between them.
Is this possible?
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
No file, test, or entry point is named. Start by clarifying the desired project-based network configuration and the Docker networking behavior required for containers in different projects. Done means containers from different projects cannot access one another while the existing project workflow remains usable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- devops, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 32/100