Oracle is pleased to announce the Oracle Container Runtime for Docker Release 17.06. Oracle Container Runtime allows you to create and distribute applications across Oracle Linux systems and other operating systems that support Docker. Oracle Container Runtime for Docker consists of the Docker Engine, which packages and runs the applications, and integrates with the Docker Hub, Docker Store and Oracle Container Registry to share the applications in a Software-as-a-Service (SaaS) cloud.
The current release of Oracle Container Runtime for Docker is based on the upstream Docker 17.06 release and incorporates the changes present in subsequent upstream releases since the previous release. The Oracle Container Runtime for Docker Release 17.06 is available on Oracle Linux 7 (x86_64) and is an upgrade to the previous release provided by Oracle.
One of the most significant new features in Oracle Container Runtime for Docker is support for multi-stage builds. This allows users to create a Dockerfile that creates intermediate build artifacts for the final image but which do not need to be included in the final image itself. This can help to reduce image sizes as well as improve load times and performance of running containers. More information on multi-stage builds can be found in Oracle Container Runtime for Docker User's Guide.
Other improvements to the build environment include the ability to use build-time arguments in the form of ARG instructions in a Dockerfile, which allows you to pass environment variables into each image. FROM instructions support variables defined in ARG instructions that precede them in the Dockerfile.
In this release, the overlay2 storage driver is supported in conjunction with SELinux. In previous releases, the Docker Engine did not start when SELinux was enabled and an overlay file system was in use. This check has been dropped as newer kernels have support for this combination and the packages for SELinux support have been updated.
Also included in this release is the docker-storage-config utility, that can be used to help new users correctly set up Docker storage for a new installation, so that the configuration follows Oracle guidelines. See Using the docker-storage-config Utility to Automatically Configure Docker Storage for more information.
Note that this release disables communication with legacy registries, running the v1 protocol by default. While it is possible to allow communication using this version of the protocol by setting the --disable-legacy-registry=false daemon option, support for v1 registries is deprecated.
The --graph daemon option is also deprecated in favor of the --data-root option, as this is more descriptive and less confusing. The option indicates the path of the parent directory that contains data for images, volumes, containers, networks, swarm cluster state and swarm node certificates.