Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1330595 - /usr/bin/docker wrapper script: $@ must be quoted
/usr/bin/docker wrapper script: $@ must be quoted
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: docker (Show other bugs)
7.2
Unspecified Unspecified
urgent Severity urgent
: rc
: ---
Assigned To: Lokesh Mandvekar
atomic-bugs@redhat.com
: Extras
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2016-04-26 10:26 EDT by Ed Santiago
Modified: 2016-05-12 11:18 EDT (History)
3 users (show)

See Also:
Fixed In Version: docker-1.9.1-34.el7
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-05-12 11:18:24 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2016:1034 normal SHIPPED_LIVE Moderate: docker security, bug fix, and enhancement update 2016-05-12 15:15:01 EDT

  None (edit)
Description Ed Santiago 2016-04-26 10:26:02 EDT
docker-common-1.9.1-33.el7 introduces /usr/bin/docker as a wrapper script that selects between docker-current and docker-latest. The exec line currently reads:

   exec ${DOCKERBINARY} $@

The $@ is missing double quotes. It should be: "$@" (double-quote, dollar, at, double-quote). See 'Special Parameters' in bash(1) for really-kind-of-inadequate explanation, but basically, without the double-quotes, you lose information about individual params and/or spaces within params.
Comment 1 Lokesh Mandvekar 2016-04-26 10:43:52 EDT
fix upcoming ...
Comment 2 Daniel Walsh 2016-04-26 10:56:13 EDT
Lokesh can you handle the situation where docker-latest is installed but docker is not?  Or does docker-latest require docker?
Comment 3 Lokesh Mandvekar 2016-04-26 11:01:19 EDT
docker-latest does require docker-common and people could edit /etc/sysconfig/docker to point it to /usr/bin/docker-latest, or do you want this pointing to /usr/bin/docker-latest to be automatic if we only have docker-common and docker-latest installed?
Comment 4 Daniel Walsh 2016-04-26 13:06:43 EDT
Well docker command will fail if there is nothing set in /etc/sysconfig/docker.  Which might be fine, but we should enhance the script to point this out as an error. Or for now make the script look for /usr/bin/docker-common followed by searching for /usr/bin/docker-latest.

We still have an /etc/sysconfig/docker-latest, correct?
Comment 5 Lokesh Mandvekar 2016-04-26 13:12:25 EDT

(In reply to Daniel Walsh from comment #4)
> Well docker command will fail if there is nothing set in
> /etc/sysconfig/docker.  Which might be fine, but we should enhance the
> script to point this out as an error. Or for now make the script look for
> /usr/bin/docker-common followed by searching for /usr/bin/docker-latest.

See: https://bugzilla.redhat.com/show_bug.cgi?id=1330622#c4

> 
> We still have an /etc/sysconfig/docker-latest, correct?

Yes

Also, should DOCKERBINARY be set in a new /etc/sysconfig/docker-common instead, or does it suffice to have it in /etc/sysconfig/docker itself (latter means less work for me)
Comment 7 Daniel Walsh 2016-04-26 13:59:58 EDT
Just put the entry in /etc/sysconfig/docker
Comment 9 Luwen Su 2016-04-30 23:46:06 EDT
In docker-1.9.1-38.el7.x86_64
#cat /usr/bin/docker
exec ${DOCKERBINARY} "$@"

Move to verified
Comment 11 errata-xmlrpc 2016-05-12 11:18:24 EDT
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/RHSA-2016-1034.html

Note You need to log in before you can comment on or make changes to this bug.