Hide Forgot
Description of problem: # /usr/lib/docker-latest/docker-latest-novolume-plugin # ls /var/run/docker/plugins/ docker-novolume-plugin.sock It would be better to created a socket called docker-latest-novolume-plugin.sock instead for consistent to match the value passed into /etc/sysconfig/docker-latest conf file. If they don't match, it will error out, # docker-latest run -v /:/test fedora sh docker: Error response from daemon: plugin docker-latest-novolume-plugin failed with error: plugin not found. Version-Release number of selected component (if applicable): docker-latest-novolume-plugin-1.10.3-9.el7.x86_64 How reproducible: always
fixed in upcoming ...
Still error out, # docker-latest info Error response from daemon: plugin docker-latest-novolume-plugin failed with error: plugin not found The socket file was created under, /run/docker-latest/plugins/docker-latest-novolume-plugin.sock However, docker-latest daemon still look for one under, /run/docker/ A workaround is, # ln -s /run/docker-latest/plugins /run/docker/plugins # docker-latest info <Working fine.> Sigh, the plugin directory seems hard-coded to /run/docker since passed -exec-root /run/docker-latest does not help.
This package should not exist. There should be no plugins that are called docker-latest. docker-latest should only change docker code and the docker-storage-setup.
I have an idea why the socket is created in the wrong directory though. Will look more into it later today.
(In reply to Daniel Walsh from comment #5) > This package should not exist. There should be no plugins that are called > docker-latest. docker-latest should only change docker code and the > docker-storage-setup. Plugin subpackages only have docker- prefixed now.
Lets close this as fix now.
Fine to me in docker-latest-1.10.3-22.el7.x86_64 # docker-latest info Containers: 0 Running: 0 Paused: 0 Stopped: 0 Images: 0 Server Version: 1.10.3 # rpm -qa | grep -i novolume-plugin docker-novolume-plugin-1.10.3-22.el7.x86_64 move to verified
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHEA-2016-1057.html