Page MenuHomeSolus

Docker defaults to using outdated storage driver
Closed, ResolvedPublic

Description

A while ago, the Docker package was configured to use the overlay storage driver. The overlay storage driver has now been replaced by the overlay2 driver.

Unless there is a reason not to, I recommend we move to overlay2, as I ran into a number of time sink issues on account of using overlay1. All that needs to be changed, is that systemd's Exec start needs to be:

ExecStart=/usr/bin/dockerd --storage-driver=overlay2 -H fd://

Instead of:

ExecStart=/usr/bin/dockerd --storage-driver=overlay -H fd://

That being said, is there a reason for using the outdated driver?

Event Timeline

David_D created this task.Feb 28 2019, 8:02 AM
Herald removed JoshStrobl as the assignee of this task. · View Herald TranscriptFeb 28 2019, 8:02 AM
Herald added a subscriber: JoshStrobl.

I simply didn't know about the difference and didn't have any issues, I'll patch it.

Wonderful. Yes, it is a very, very obscure issue. I believe this version of the storage driver didn't exist when the storage driver fix was first implemented.