Docker Community Forums

Share and learn in the Docker community.

Failing to connect to linked container when app boot is too fast


(Brian Morton) #1

I kept getting an error of “no route to host” when my service was launching and attempting to connect to a linked service. When I fired up the terminal and connected manually, it always worked. This made me think that networking wasn’t yet available when my container booted and sure enough, if I add a 5 second sleep to my application’s boot process, the “no route to host” error goes away.

Is this a known issue?


(Vidsy.co (Charlie)) #2

This is a general issue w/ Docker.

@revett


(Brian Morton) #3

I think that’s a little different from what I’m seeing. I have scripts that are expecting “ethwe” to be available and it isn’t available until around 5 seconds after the container has launched. Is that expected?