[FOLIO-2404] Docker port mapping doesn't work in FOLIO CI Created: 17/Dec/19 Updated: 03/Jun/20 Resolved: 24/Feb/20 |
|
| Status: | Closed |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Task | Priority: | P3 |
| Reporter: | John Malconian | Assignee: | John Malconian |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | platform-backlog | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||
| Sprint: | CP: sprint 79, DevOps: sprint 82 | ||||||||
| Development Team: | FOLIO DevOps | ||||||||
| Description |
|
Since Jenkins builds run in docker containers, it is difficult to run tests that create other sibling containers when port mapping is enabled on the sibling container. This is because ports are mapped to the Docker host system and not the container spawning the sibling container. e.g. When either 0.0.0.0:9131 or 127.0.0.1:9131 is mapped to the host system, the build container is unable to connect because it thinks those are local addresses (local to the container). |
| Comments |
| Comment by John Malconian [ 17/Dec/19 ] |
|
To communicate with sibling containers from the build container, normally you would connect directly the sibling container's IP and service port - essentially bypassing port mapping. However, I'm not sure if this is sufficient for certain kinds of tests that need to test port mapping (
|
| Comment by John Malconian [ 24/Feb/20 ] |
|
Not necessary. |