Docker container runtime fails to start with 'Base Device UUID and Filesystem verification failed'

Solution Verified - Updated -

Issue

  • The docker service will not start
  • The journal for docker.service provides this failure:
Aug 15 09:05:21 example.com dockerd-current[4214]: time="2017-08-15T09:05:21.881789151-06:00" level=fatal msg="Error starting daemon: error initializing graphdriver: devmapper: Base Device UUID and Filesystem verification failed: devicemapper: Error running deviceCreate (ActivateDevice) dm_task_run failed"
Aug 15 09:05:21 example.com systemd[1]: docker.service: main process exited, code=exited, status=1/FAILURE
Aug 15 09:05:21 example.com systemd[1]: Failed to start Docker Application Container Engine.
Aug 15 09:05:21 example.com systemd[1]: Unit docker.service entered failed state.
Aug 15 09:05:21 example.com systemd[1]: docker.service failed.

Environment

  • Red Hat Enterprise Linux 7
  • Red Hat Enterprise Linux Atomic Host

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