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.

docker-1.12.0-6.el7.x86_64 fresh install. Some docker commands fail with:

    /usr/bin/docker-current: Error response from daemon: driver failed programming external connectivity on endpoint [name] (sha): exec: "docker-proxy": executable file not found in $PATH.

docker provides /usr/bin/docker-proxy-current but no docker-proxy.

Failing commands are part of the docker-autotest suite, and it's only a few commands. I'm not sure what the commonality is, and haven't bothered to extract a reproducer but I will do so on request.

docker-proxy should be named just "docker-proxy" not current (same as docker-runc and docker-containerd). Assigning to Lokesh to rebuild for RHEL with "-current" suffix.

(In reply to Antonio Murdaca from comment #2)
> docker-proxy should be named just "docker-proxy" not current (same as
> docker-runc and docker-containerd). Assigning to Lokesh to rebuild for RHEL
> with "-current" suffix.

so how does this work if both docker and docker-latest need to ship docker-proxy? I guess we can remove it from one of the packages if both are shipping the same version, but what about the case where you have different versions?

It's being installed as just 'docker-proxy' for now in docker-latest while docker still doesn't need to worry about it because 1.10.3

Confirmed as fixed in 1.12.0-4.el7

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/RHBA-2016-1829.html