Docker isn't perfect – Issue #216

Re:Docker isn't perfect – Issue #216 by scurvy on Friday August 28, 2015 @09:46PM (#10138677)

Someone tell that to RedHat. They consider the network "up" once the device gets link, not when the system gets an IP address. Even in environments without spanning tree, this is a problem due to massive parallelization -- spawning 30 processes 5ms after the network is "up" but doesn't have an IP from DHCP yet.

The solution? Put a sleep 7 in there, thus making the entire process slower than the previous solution.

[ Parent | on HN ]

Re:Docker isn't perfect – Issue #216 by ibotty on Tuesday September 01, 2015 @03:33AM (#10151164)

That's wrong. Read about it at https://wiki.freedesktop.org/www/Software/systemd/NetworkTar...

[ Parent | on HN ]

Re:Docker isn't perfect – Issue #216 by scurvy on Wednesday September 02, 2015 @11:29AM (#10159879)

So either I use systemd's sleep or my sleep, but either way it's broken out of the box. Great job!

EDIT: RHEL/CentOS only supports NetworkManager for this. Which sucks if you don't want to run NetworkManager (for a litany of reasons).

$ yum whatprovides "*/systemd-networkd-wait-online.service" No matches found

[ Parent | on HN ]

Re:Docker isn't perfect – Issue #216 by crdoconnor on Saturday August 29, 2015 @05:57AM (#10139534)

Wow, that's disgusting.

[ Parent | on HN ]