Icinga / Icinga/icinga-testing
Create port forwardings in Docker to access services from the test cases
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1
- Forks
- 2
- Avg merge
- 15h 36m
- Merged PRs (30d)
- 11
Description
The current implementation relies on the container addresses to be reachable from the host as is the case when running Docker on Linux with bridge networking. However, this doesn't work on Mac OS and probably also Windows. To be able to natively run the tests there, it's necessary to create a port forwarding for each container port and then distinguish between access from the host and from another container for each use of address/port information.
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 container addresses and ports are used by the test cases and where Docker containers are created. Compare host access with container-to-container access, then verify the tests can reach forwarded service ports on macOS and Windows while preserving internal container connectivity.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- infrastructure, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100