moby: docker 1.7 not starting: [graphdriver] prior storage driver "aufs" failed

Since the upgrade to version 1.7 docker does not start anymore at boot. The error message in /var/log/upstart/docker.log is

/var/run/docker.sock is up
INFO[0000] Listening for HTTP on unix (/var/run/docker.sock) 
ERRO[0000] [graphdriver] prior storage driver "aufs" failed: backing file system is unsupported for this graph driver 
FATA[0000] Error starting daemon: error initializing graphdriver: backing file system is unsupported for this graph driver

Other system info:

os: ubuntu 14.04 LTS,
docker installed via
```
wget -q0- https://get.docker.com/ | sh
```
docker version docker -v:
```
Docker version 1.7.0, build 0baf609
```

About this issue

Original URL
State: closed
Created 9 years ago
Comments: 18 (5 by maintainers)

Most upvoted comments

OK. I just removed the subfolder aufs and the file repositories-aufs and then I issued a

service docker start

it works again!

Thank you all (for your quick brainstorming and responses)!

andibachmann on Jul 6, 2015

Hi!

Please read this important information about creating issues.

If you are reporting a new issue, make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead.

If you suspect your issue is a bug, please edit your issue description to include the BUG REPORT INFORMATION shown below. If you fail to provide this information within 7 days, we cannot debug your issue and will close it. We will, however, reopen it if you later provide the information.

This is an automated, informational response.

Thank you.

For more information about reporting issues, see https://github.com/docker/docker/blob/master/CONTRIBUTING.md#reporting-other-issues

BUG REPORT INFORMATION

Use the commands below to provide key information from your environment:

docker version: docker info: uname -a:

Provide additional environment details (AWS, VirtualBox, physical, etc.):

List the steps to reproduce the issue: 1. 2. 3.

Describe the results you received:

Describe the results you expected:

Provide additional info you think is important:

----------END REPORT ---------

#ENEEDMOREINFO

GordonTheTurtle on Jul 6, 2015