Docker daemon is not able to start after an update.

Solution Verified - Updated -

Issue

  • After upgrading from docker-latest to docker, docker daemon fails to start with the below errors:
Job for docker.service failed because the control process exited with error code. See "systemctl status docker.service" and "journalctl -xe" for details

Jun 09 08:08:42 duskapp1541d2.eb.lan.at systemd[1]: Starting Docker Application Container Engine...
Jun 09 08:08:42 duskapp1541d2.eb.lan.at dockerd-current[32347]: time="2020-06-09T08:08:42.283610583+02:00" level=info msg="libcontainerd: new containerd process, pid: 32355"
Jun 09 08:08:43 duskapp1541d2.eb.lan.at dockerd-current[32347]: Error starting daemon: invalid argument
Jun 09 08:08:43 duskapp1541d2.eb.lan.at systemd[1]: docker.service: main process exited, code=exited, status=1/FAILURE
Jun 09 08:08:43 duskapp1541d2.eb.lan.at systemd[1]: Failed to start Docker Application Container Engine.
Jun 09 08:08:43 duskapp1541d2.eb.lan.at systemd[1]: Unit docker.service entered failed state.
Jun 09 08:08:43 duskapp1541d2.eb.lan.at systemd[1]: docker.service failed.

Environment

  • Red Hat Enterprise Linux (RHEL) 7
  • docker-1.13.1-161.git64e9980.el7_8.x86_64 and above.

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