RHEA-2016:1057 - Product Enhancement Advisory

Topic

New docker-latest packages are now available for Red Hat Enterprise Linux 7 Extras.

Description

Docker is an open-source engine that automates the deployment of any application as a lightweight, portable, self-sufficient container that will run virtually anywhere.

The docker-latest packages contain Docker version 1.10.3. This enhancement update adds the docker-latest packages to Red Hat Enterprise Linux 7 Extras. For more information about docker-latest, see the Red Hat Enterprise Linux 7.2 Release Notes, linked from the References section.(BZ#1325388)

The docker-latest packages also contain the following enhancements:

• Support for bind mounts at docker build time has been added to docker-latest. Now, a docker build accepts bind mounts with the "-v" flag. Data can be shared between the host and the build environment. (BZ#1126669, BZ#1121667)
• The /usr/bin/docker script now calls /usr/bin/docker-latest by default if docker is not installed. /usr/bin/docker and /etc/sysconfig/docker provided by the docker-common package allow you to configure which docker client binary gets called. /usr/bin/docker will call /usr/bin/docker-latest by default when docker is not installed. If docker is installed, /usr/bin/docker will call /usr/bin/docker-current by default, unless DOCKERBINARY is set to /usr/bin/docker-latest in /etc/sysconfig/docker. This way, you can use docker-latest or docker without the need to check which version of the daemon is currently running. (BZ#1330366)
• If you are running systemd as PID1 inside of a container, in order to get it to shut down correctly, you need to send it the proper signal. By default, docker sends PID1 SIGTERM, but now you can specify the stop-signal using the "--stop-signal" flag in the following way:

docker run --stop-signal=RTMIN+3

This command will send the RTMIN+3 signal to PID1 when executing docker stop. If systemd is running as PID1 it will shut down correctly. (BZ#1201657)

All users who require docker-latest are advised to install these new packages.

Solution

Before applying this update, make sure all previously released errata
relevant to your system have been applied.

For details on how to apply this update, refer to:

https://access.redhat.com/articles/11258

Affected Products

• Red Hat Enterprise Linux Server 7 x86_64
• Red Hat Enterprise Linux Server from RHUI 7 x86_64

Fixes

• BZ - 1097344 - Docker run exit code consistency
• BZ - 1201657 - Running docker stop does not properly stop systemd-container-based container, SIGTERM causes reexecution
• BZ - 1273598 - docker looses /etc/hosts
• BZ - 1286326 - docker timeouts when waiting for mkfs to finish on devicemapper storage driver device
• BZ - 1291852 - docker info Backing Filesystem for devicemapper is an empty string
• BZ - 1302408 - Docker 1.9 performance issues
• BZ - 1325388 - [extras-rhel-7.2.4] include "docker-latest" as new package in RHEL 7.2
• BZ - 1326374 - several files out-of-sync
• BZ - 1327309 - docker-novolume-plugin created an unix socket with a confused name.
• BZ - 1327314 - [extras-rhel-7.2.4] include rhel-push-plugin as a subpackage in docker 1.10 and higher
• BZ - 1327405 - [extras-rhel-7.2.4] include docker-lvm-plugin as a subpackage in docker 1.10 and higher
• BZ - 1327679 - seccomp: config provided but seccomp not supported
• BZ - 1328220 - [extras-rhel-7.2.4] Docker does not own /usr/lib/docker-storage-setup
• BZ - 1328588 - docker-lvm-plugin never work
• BZ - 1328684 - listen unix /run/docker/plugins/rhel-push-plugin.sock: bind: no such file or directory
• BZ - 1330366 - [extras-rhel-7.2.4] docker-latest should Requires: docker-common
• BZ - 1330714 - docker-storage-setup frequently fails when lvm2 not initially installed in system
• BZ - 1331855 - docker-latest-storage-setup fails with error "not a valid identifier"
• BZ - 1333123 - [extras-rhel-7.2.4] include ADD|BLOCK_REGISTRY variables in docker-latest sysconfig

CVEs

(none)

References

• http://www.redhat.com/security/updates/classification/#normal