2 ms·
Too bad almost all containers rely on bridged networking and different ports. Why not just bind to 127.0.x.y, where x is the project number, and y is the machin
by jbverschoor 4y ago
Too bad almost all containers rely on bridged networking and different ports. Why not just bind to 127.0.x.y, where x is the project number, and y is the machine number. That way, you can just use default ports
- deleted 4y ago[deleted]
- Eleison23 4y agoBecause the loopback address doesn't work like that. 127.0.0.0/8 is defined as all loopback, which means the OS shouldn't differentiate between them, so any VMs binding on 127.* are going to interfere with the OS binding there.
- jbverschoor 4y agoAny other (local) range would be fine. 127.* does seem to have some strange behaviors