search

katharostech / docker-plugin_lizardfs

Docker volume plugin for mounting LizardFS
Other
19 stars 2 forks source link

Networking Broken on Docker 18.06 #3

Open zicklag opened 6 years ago

zicklag commented 6 years ago

I just upgraded Docker on one of my Swarm hosts and I found that it seems Docker changed part of the swarm networking strategy so that the master does not recognized the chunkserver IP addresses correctly. There is some additional invisible container that joins to the swarm overlay network called lb-[network name] and the LizardFS master sees the chunkservers as joining to the master under that containers IP instead of the proper container IP.

I haven't done much research on this yet. For now I am just rolling back to Docker 18.03 and that fixed the issue. This problem should be fixed when I find time to refactor the plugin for Swarm.

johny-mnemonic commented 6 years ago

I tried to delve a bit into this and it looks like they started using ingress for resolving internal request, which is weird. More details in this weave issue. Someone mentions that it is not broken in 18.03 as well. Which brings me to the typo you have in the name of this issue. It seems to be broken in 18.06 and working in 18.03;-)

zicklag commented 6 years ago

@johny-mnemonic Whoops. Fixed the title. :D

Yeah, that kind of looks like a Docker bug to me, or at least a very strange decision that seems like it would break a lot of stuff. Thanks for the lead.

DanielUranga commented 5 years ago

I'm experiencing exactly this same issue, was working in Docker 18.03.

zicklag commented 5 years ago

You can try to run the swarm services in host networking mode. This worked for another user.

SvenDowideit commented 5 years ago

@zicklag is this still a problem with current docker swarm? I was trying to setup a lizardfs cluster like I have in https://github.com/onaci/docker-plugin-seaweedfs/blob/golang/seaweedfs.yml - fully in a private overlay network, used only for serving storage to the swarm via the volume plugin.

I expect that the work I'm doing in the seaweedfs volume plugin will be able to be applied to lizardfs just as easily as you did - so it would be really cool to compare them.