search

katharostech / docker-plugin_lizardfs

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

[Discussion] Plugin Networking Options #7

Open zicklag opened 5 years ago

zicklag 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.

_Originally posted by @SvenDowideit in https://github.com/kadimasolutions/docker-plugin_lizardfs/issues/3#issuecomment-515442785_

zicklag commented 5 years ago

@svenDowideit I think that it is still a problem but I haven't tested it recently.

Were you able to get the SeaweedFS Docker plugin to communicate with the SeaweedFS master on the overlay network? The problem I had when I tried to do that is that Docker plugins have to run on the host network because are actually created before all of the other Docker features such as the overlay networking system even exists. My workaround at the time was to actually run the plugin inside of a privileged container on the Swarm overlay, instead of using a Docker 2.0 plugin that could be installed with docker plugin install. That didn't work very well and the best option ended up being to run everything on the host network so that the Docker 2.0 plugin could access it on the host network.

If you somehow got a Docker plugin that could be installed with docker plugin install to succesfully commmunicate on an overlay network, that would be great.

SvenDowideit commented 5 years ago

Sadly no - though there was a discussion on the docker community slack in the #plugins channel about that being a desired feature :)

I went another way - I want the plugin to also be the storage stack operator - so mount the docker socket into the plugin, and then work via an intermediary container

I expect things will change over time, as we figure out what advanced things plugins can do, and what we need the plugins api to do...

Sven

On Sat, Jul 27, 2019 at 12:43 AM Zicklag notifications@github.com wrote:

@SvenDowideit https://github.com/SvenDowideit I think that it is still a problem but I haven't tested it recently.

Were you able to get the SeaweedFS Docker plugin to communicate with the SeaweedFS master on the overlay network? The problem I had when I tried to do that is that Docker plugins have to run on the host network because are actually created before all of the other Docker features such as the overlay networking system even exists. My workaround at the time was to actually run the plugin inside of a privileged container on the Swarm overlay, instead of using a Docker 2.0 plugin that could be installed with docker plugin install. That didn't work very well and the best option ended up being to run everything on the host network so that the Docker 2.0 plugin could access it on the host network.

If you somehow got a Docker plugin that could be installed with docker plugin install to succesfully commmunicate on an overlay network, that would be great.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/kadimasolutions/docker-plugin_lizardfs/issues/7?email_source=notifications&email_token=AAAG6TAUEUIJSWR5VHR4C4TQBMEPDA5CNFSM4IHEM372YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD24Z54A#issuecomment-515481328, or mute the thread https://github.com/notifications/unsubscribe-auth/AAAG6TAE5IUCFEPHMJ6LZPLQBMEPDANCNFSM4IHEM37Q .