Daemon.json being modified to use overlay2 doesnt work

Docker Engine General
1

Editing the daemon.json copy pasted original from this documentation page doesn’t work and doesn’t let docker start:

{
  "storage-driver": "overlay2"
}

Any way to get help? Logs are here:

░ The job identifier is 10512 and the job result is failed.
Nov 02 13:14:42 ubuntu systemd[1]: docker.service: Scheduled restart job, resta>
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ Automatic restarting of the unit docker.service has been scheduled, as the r>
░░ the configured Restart= setting for the unit.
Nov 02 13:14:42 ubuntu systemd[1]: docker.service: Start request repeated too q>
Nov 02 13:14:42 ubuntu systemd[1]: docker.service: Failed with result 'exit-cod>
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ The unit docker.service has entered the 'failed' state with result 'exit-cod>
Nov 02 13:14:42 ubuntu systemd[1]: Failed to start docker.service - Docker Appl>
░░ Subject: A start job for unit docker.service has failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ A start job for unit docker.service has finished with a failure.
░░ 
░░ The job identifier is 10605 and the job result is failed.

Sorry if that log was excessive

2

Please, share the logs without truncating the end. You can do it by passing --no-pager to the hournalctl command.

I don’t expect anything important there but let’s make sure. What I see is the error message saying you had too many restarts. It is not the original error message. I wanted to make a blogpost about solving this, but I could not reproduce the missing details as the daemon stopped after two or three retries. So please, share your docker environment details as well, but usually you need to back to odler logs to see the original issue like the driver is not supported.

We usually need the following information to understand the issue:

  1. What platform are you using? Windows, Linux or macOS? Which version of the operating systems? In case of Linux, which distribution?

  2. How did you install Docker? Sharing the platform almost answers it, but only almost. Direct links to the followed guide can be useful.

  3. On debian based Linux, the following commands can give us some idea and recognize incorrectly installed Docker:

    docker info
docker version

    Review the output before sharing and remove confidential data if any appears (public IP for example)

    dpkg -l 'docker*' | grep '^ii'
snap list docker

    When you share the outputs, always format your posts according to the following guide: How to format your forum posts

3

It randomly works now, thanks for trying to help though

4

By “randoml” you mean you can’t explain but it suddenly works now, or that it works sometimes, but not always?

5

From the shared logs we can derive two things:

  • Ubuntu is used
  • Since the support url points to the ubuntu.com domain, you must be using the docker.io package from ubuntu’s repositories or the docker snap package.

The default Ubuntu kernels support overlay2 out of the box. With vanilla docker, It should have been picked up as storage driver.

If you run a self-compiled kernel (or a different Linux disto), you can verify if all required kernel modules are available:

wget -O - https://github.com/moby/moby/raw/master/contrib/check-config.sh  | sh
1 Like