Server version v0 14 3 breaks docker s ability to be an egre

Question

Server version v0 14 3 breaks docker s ability to be an egress gateway Any quick fixes

jolly-london-20127 · Answer

< echoing controller 96073> have you tested yet to confirm

echoing-controller-96073 · Answer

yes In v0 14 3 I was getting a destination host unreachable when trying to ping but in my latest develop it pings just fine

jolly-london-20127 · Answer

hmmm interesting < bored island 21407> did you push anything to develop that might affect this

echoing-controller-96073 · Answer

left side is 0 14 3 right side is develop docker logs and journalctls

bored-island-21407 · Answer

nope the only thing new in develop is your hotfix

jolly-london-20127 · Answer

hmmm so sounds like maybe the route only populates under certain conditions

shy-family-23356 · Answer

I have not much experience with this The only thing I notice here is the routing table has changed in Netclient Docker Left is with server 0 14 2 right with 0 14 3

shy-family-23356 · Answer

10 192 130 0 24 is the subnet which I try to expose with the windows netclient docker