Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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
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.
(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.
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