Too many open files

[matchbooklab]

Too many open files

[CWSpear]

I am curious: Why are you using this plugin with Swarm? That wasn't really the intended use-case, since this plugin is specifically intended for local persistence of a single host, and not designed to work with multi-host instances like when using Swarm.

[mwilmes]

To my understanding Swarm isn't changing the picture per-se. It's acting more like a proxy. Persistence should still be within the local Docker daemon scope. For what I know Docker volume plugins interact with the local daemon only, isn't that right?

[CWSpear]

I am not sure what you mean by "local daemon" since the daemon only runs on the server (I'd call that "remote," not "local"), and that's where you need the plugin running. So if you're using a plugin with Swarm, every server in the cluster would need the plugin running (and the client does not).

[mwilmes]

Sorry for the misunderstanding. This is exactly how my setup looks like.

[CWSpear]

This appears to be related to #20. Not really sure what's going on, but does seem to be related to something Swarm does.

[luckyraul]

any updates?

[CWSpear]

No updates. I only have reports that this happens when using this with Swarm. I am not sure where this plugin really fits in in a Swarm setup, so I am having a hard time trying to understand what's going on.

[CWSpear]

I'm gonna go ahead and close this for inactivity.

If someone wants to further write on how they're using this with Swarm and why, I'd be happy to continue the discuss. Until then, I feel like this is a nonissue since it's outside the plugin's use-case as far as I understand it.