Closed wilsontayar closed 7 years ago
Assuming you're running this container in host networking mode (which you should be) then the changes in v1.2.x shouldn't have an impact - but hey, you never know.
Could you post the beginning of the logs please? From the above it looks like keepalived is already running before the script starts it, which it shouldn't be but perhaps some of the looping logic in the entrypoint script is subtly flawed.
For some reason, chk_haproxy wasn't getting port 80 when running ss -ltn 'src any'
.
I didn't have time to investigate it further, but I guess the new Rancher's LB might have something to do with it.
Anyway, I've changed to a port that appeared when running ss -ltn
from inside the container (eg. 22) and everything seems to be working just as before the update.
Thanks for the assistance, @sjiveson. I'm closing the issue now. :)
OK, good stuff and you're welcome. Hope you get to the bottom of why the port is missing.
Hey guys,
I've just updated my rancher server to the latest version (v1.2.1) on a CoreOS host (stable 1185.5.0) and now my keepalived container does not seem to be working.
Maybe this has something to do with Rancher's new network service?
Here's the container logs: