-
Notifications
You must be signed in to change notification settings - Fork 222
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Docker plugins not enabled after host reboot or docker service restart #129
Comments
Can confirm that I'm seeing the same behavior:
We're using ontap-nas with NFS mounts, and I initially thought it was caused by rpc-statd not having been started. However, that was not the case — after adding rpc-statd.service as a "Wants" dependency of the docker.service and then rebooting, the rpc-statd errors cleared (as expected) but the trident plugin was still disabled. Another oddity is that Docker created the trident volumes with the "local" driver, which led to name conflicts after enabling the trident plugin. |
We reverted back to 18.01 to dodge around this |
Also seeing this. It's been quite some time without any word from devs. Any work being done for this? This bug makes claims that this driver is "ready for production" quite questionable. |
Does it really? We've been looking into this for a while. Unfortunately Docker unexpectedly introduced a number of tight timeouts in their 18.03 release that forced us to re-architect Trident's entire initialization process. Much of that work was done in 18.04, and improvements have been made in 18.07, but there appear to be some additional timing gaps that are unaccounted for that we're working to close. |
@silentpete Thank you for breaking your silence to let us know! We are working feverishly to get our official 18.07 release out by end of July, so should be any day now. |
@korenaren your welcome! 👍 Cool!! |
I verified that with Trident 18.01, when the host or docker service is restarted the plugins are automatically enabled. With Trident 18.04, the plugins are disabled and have to be manually enabled. This is reproducible with the following:
The text was updated successfully, but these errors were encountered: