Job "docker.service/start" failed with result 'dependency' when using an custom insecure registry

Solution Verified - Updated -


  • When trying to start the docker.service in an OCP master node, it fails with the following error message:

    # systemctl start docker
    A dependency job for docker.service failed. See 'journalctl -xe' for details.
  • The registries.service status has the following error message:

    # systemctl status registries
    Feb 14 09:20:35 systemd[1]: Starting SystemWide Container Registries...
    Feb 14 09:20:35 registries[43156]: Unable to load and parse /etc/containers/registries.conf
    Feb 14 09:20:35 registries[43156]: .
    Feb 14 09:20:35 systemd[1]: registries.service: main process exited, code=exited, status=1/FAILURE
    Feb 14 09:20:35 systemd[1]: Failed to start SystemWide Container Registries.
    Feb 14 09:20:35 systemd[1]: Unit registries.service entered failed state.
    Feb 14 09:20:35 systemd[1]: registries.service failed.


  • Red Hat OpenShift Container Platform (OCP)
    • 3.9
  • Red Hat Enterprise Linux (RHEL)
    • 7.x

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