Updated docker packages that fix several bugs are now available for Red HatEnterprise Linux 7.

Docker is an open-source engine that automates the deployment of any applicationas a lightweight, portable, self-sufficient container that will run virtuallyanywhere. This update fixes the following bugs:* When running the docker client, the client attempts to create a .dockerdirectory in the directory indicated by the $HOME environment variable and writecertificate data into it. If the $HOME environment variable is not set, dockerattempts to create /.docker. On an Atomic Host, the / directory is notwriteable, so the service failed with a permission denied error message. Withthis update, the docker client attempts to write to its configuration data tothe home directory for the executing user if $HOME is not set. If that fails,the docker client will fall back to trying the /etc/docker directory.(BZ#1198599)* Previously, the docker service put the 80-docker.rules file in the/etc/udev/rules.d/ directory. This directory is used for the administrator’sudev rules. This update fixes the location, and the 80-docker.rules file is nowcorrectly stored in the /usr/lib/udev/rules.d/ directory. (BZ#1199433)* When docker images have directories specified as “externally mounted” (thatis, the VOLUME keyword is present in a Dockerfile, and the{{.ContainerConfig.Volumes}} entry in docker inspect), the SELinux policy for/var/lib/docker/vfs/dir/* files was set incorrectly. As a consequence,the containers could not store data on these volumes. This update adds thecorrect SELinux policy for the files in /var/lib/docker/vfs/dir/*, and thecontainers can now store data as intended. (BZ#1193700)* Previously, if a host volume was mounted after starting the docker service andthen the mapping was carried out inside the container, the volume failed tomount. In addition, if the volume was unmounted on the host, docker daemon stillreported the mounted files. For both of these scenarios, restarting the dockerservice after mounting the volume led to correct mapping inside the dockercontainer. The incorrect behavior of the docker daemon, which changed the mountnamespaces and ignored the host, has been fixed, and the host volume is nowcorrectly mounted in the described situations. (BZ#1180718) Users of docker are advised to upgrade to these updated packages, which fixthese bugs.
Before applying this update, make sure all previously released erratarelevant to your system have been applied.For details on how to apply this update, refer to:https://access.redhat.com/articles/11258
1097189 – docker fail to start because of existing container id1113085 – `docker run` doesn’t exit properly in interactive mode1169327 – docker run fails with “SQL error or missing database: no such table: entity”1188318 – atomic run fedora /bin/sh is broken1192312 – Wrong versions of docker 1.5.0-1 sub rpm1194445 – docker-python in RHEL 7.1 does not work with version of python-requests shipped in RHEL7.11196709 – docker run -it –rm empty fatal error1197158 – ADD_REGISTRY support is broken in 1.5.0-61198599 – docker command will not execute within a systemd unit file on a atomic host1198630 – docker doesn’t work for images from docker.io1199433 – 80-docker.rules should be in /usr/lib/udev/rules.d/1200023 – docker 1.5.0 is available1200104 – dns resolution is broken inside containers with selinux enforced1200394 – “atomic run –spc” fails in latest docker builds due to problems mapping /run/ into container1202517 – docker fd leak1204576 – docker-fetch isn’t buildable

These packages are GPG signed by Red Hat for security. Our key and
details on how to verify the signature are available from:

Leave a Reply