OpenShift pod now fails with error when trying to write to secret volume

Solution Unverified - Updated -

Issue

  • Applications that write to secret, configMap, downwardAPI or projected volumes now fail with EROFS "Read-only filesystem"
  • Applications that mount a secret, configMap, downwardAPI or projected
    volume as /etc cannot start and receive an error like:

    "container init caused "rootfs_linux.go:54: mounting "/var/lib/docker/containers/some-id/resolv.conf"  to rootfs "/var/lib/docker/devicemapper/mnt/other-id/rootfs" at "/var/lib/docker-latest/devicemapper/mnt/other-id/rootfs/etc/resolv.conf" caused "open /var/lib/docker-latest/devicemapper/mnt/other-id/rootfs/etc/resolv.conf:  read-only file system"""'
    

Environment

  • Red Hat OpenShift Container Platform
    • 3.3.x versions of 3.3.1.46.11-1.git.4.e236015 or later
    • 3.4.x versions of 3.4.1.44.38-1.git.4.bb8df08 or later
    • 3.5.x versions of 3.5.5.31.48-1.git.4.ff6153e or later
    • 3.6.x versions of 3.6.173.0.96-1.git.4.e6301f8 or later
    • 3.7.x versions of 3.7.23-1.git.5.83efd71 or later
    • 3.9 and later

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.