Hacker News Reader

Docker is in very active development and issues like this get resolved every week. That said, it's not a problem because of the service discovery and routing that would be involved in the Flynn system.

View on HN

Yes, Docker is moving quickly but one barrier to resolving this is philosophical: static IPs and private networks are un-Dockerish. Right now it's not obvious what a clean solution would look like. I'd be keen to see how Flynn's discovery and routing develops, it sounds very promising.

Sounds like a job for some dynamic DNS. That's exactly the sort of thing it's supposed to solve for.

Static IPs and private networks are not particularly un-Dockerish. They are just not the default implemented by Docker :)

Docker 1.0 will include an API which will make it much easier to customize how you want networking to happen. That includes static IPs and private networks.

Note that the 1.0 API will also include hooks for service discovery - specifically to facilitate the development of projects like Flynn.

Are these feature plans documented somewhere? Private networks, in the spirit of EC2 security groups or VPCs, would help simplify many distributed computing scenarios where securing services with passwords isn't an option.

Reply on news.ycombinator.com