Docker “[graphdriver]” and ‘”aufs” failed: driver not supported’ Error After Ubuntu Upgrade

I’ve had the following error a number of times after updating Ubuntu so I figured I should post something about it (I’m bound to forget the solution) as the first “fix” I came across wasn’t actually an appropriate fix – I’ll go more into this later.

ERRO[0000] [graphdriver] prior storage driver “aufs” failed: driver not supported
FATA[0000] Error starting daemon: error initializing graphdriver: driver not supported

If you’re receiving the error above after a Ubuntu upgrade, the reason may be related to not having the correct kernel packages installed. There’s details on how to reinstall these at In a nutshell, here are the commands (you may need to reboot afterwards).

sudo apt-get update
sudo apt-get install linux-image-extra-$(uname -r) linux-image-extra-virtual

N.B. As mentioned by viker in the comments below, you may also need to perform the following command.

sudo modprobe aufs

I got this solution from the issue posted at The problem with that issue log is that the first “fix” mentioned is to remove “/var/lib/docker/aufs” which will remove your containers… this isn’t ideal. Thing is, the solution I suggest above is actually mentioned much further down the post and is only a very fleeting mention so if you’re impatient (like I am the majority of the time), you may totally miss it and delete “/var/lib/docker/aufs” in your frustration in finding an answer (proud to say I didn’t do this because deletion to fix something makes my infrastructure “spidey-sense” tingle).

3 thoughts on “Docker “[graphdriver]” and ‘”aufs” failed: driver not supported’ Error After Ubuntu Upgrade

  1. Got same issue after upgrade. apt-get update; apt-get -y installl linux-image-extra; modprobe aufs;
    shutdown -r now;
    docker working like charm 🙂

  2. I had installed Docker on my server which ran Debian Jessie. I removed Docker and upgraded my server to Debian Stretch. But the systemd configuration file /etc/systemd/system/docker.service.d/execWithDeviceMapper.conf was not removed. When I installed Docker again, it used the old systemd configuration file which had the configuration: storage-engine: devicemapper. The devicemapper storage engine does not work well with Debian Stretch. I deleted the systemd configuration file and reinstalled Docker without problems.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s