Why docker daemon fails to start with the message "Unable to take ownership of thin-pool (XXX-docker--pool) that already has used data blocks" in Red Hat Enterprise Linux 7 ?

Solution Unverified - Updated -

Issue

  • Why docker daemon fails to start with the message "Unable to take ownership of thin-pool (XXX-docker--pool) that already has used data blocks" in Red Hat Enterprise Linux 7 ?
    Details from the log
  Sep 17 17:00:01 XXXX dockerd-current: time="2017-09-17T17:00:01.522516125+10:00" level=fatal msg="Error starting daemon: error initializing graphdriver: devmapper: Unable to take ownership of thin-pool (rootvg-docker--pool) that already has used data blocks"
  Sep 17 17:00:01 XXXX systemd: docker.service: main process exited, code=exited, status=1/FAILURE

Environment

  • Red Hat Enterprise Linux 7.4
  • Existing docker installation based on docker-1.12.6-48 configured with user namespaces option as described in the documentation

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