systemd-resolved.service sometimes fails to start

Solution Verified - Updated -

Issue

When systemd-resolved.service is enabled, systemd-resolved.service sometimes fails to start at boot with the following message:

      Failed at step NAMESPACE spawning /usr/lib/systemd/systemd-resolved: Read-only file system

Environment

  • Red Hat Enterprise Linux 8

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content