The following are known Docker issues:
- Running yum install within a container on an overlayfs file system can fail with the following error:This error can break Dockerfile builds but is expected behavior from the kernel and is a known issue upstream (see https://github.com/docker/docker/issues/10180.)The workaround is to run touch /var/lib/rpm/* before installing the package.Note that this issue is fixed in any Oracle Linux images available on the Docker Hub or Oracle Container Registry, but the issue could still be encountered when running any container based on a third-party image. (Bug ID 21804564)
- Docker can fail where it uses the
overlay2
storage driver on XFS-formatted storage. A kernel patch has been applied to prevent overlay mounts on XFS if theftype
is not set to 1. This fix resolves an issue where XFS did not properly support the whiteout features of an overlay filesystem ifd_type
support was not enabled. If the Docker Engine is already using XFS-formatted storage with theoverlay2
storage driver, an upgrade of the kernel can cause Docker to fail if the underlying XFS file system is not created with the-n ftype=1
option enabled. The root partition on Oracle Linux 7 is automatically formatted with-n ftype=0
where XFS is selected as the file system. Therefore, if you intend to use theoverlay2
storage driver in this environment, you must format a separate device for this purpose. (Bug ID 25995797)
Copyright © 2019, Oracle and/or its affiliates. All rights reserved. Legal Notices
Jan 24, 2018 Mark the issue as fresh with /remove-lifecycle stale comment. Stale issues will be closed after an additional 30d of inactivity. Prevent issues from auto-closing with an /lifecycle frozen comment. If this issue is safe to close now please do so. Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.