-
Notifications
You must be signed in to change notification settings - Fork 134
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
"No such volume error" thrown by Docker daemon even when creating and returning volume info #108
Comments
After days of research I created a simple NodeJS dummy plugin that was working and analysed the communications between Docker daemon and the plugin (from NodeJS vs Go version) and found that when the field "CreatedAt" is empty (the default behavior of go-plugins-helpers) the daemon throws that error! What made it hard to discover is that this is an undocumented field from Docker docs. My suggestion is to hide it by default in responses.
I sniffed plugin communications using: ncat -lkv -U /run/docker/plugins/rbd2.sock -c 'tee /dev/stderr | ncat -v -U /run/docker/plugins/rbd.sock | tee /dev/stderr’ |
+1 |
I created a simple volume plugin and Docker daemon is throwing
"docker: Error response from daemon: error while mounting volume '': get myimage4: no such volume."
The text was updated successfully, but these errors were encountered: