# Docker with devicemapper doesn't start on CentOS 7

**URL:** <https://forums.docker.com/t/docker-with-devicemapper-doesnt-start-on-centos-7/9641>\
**Category:** General\
**Created:** [April 20, 2016, 2:59pm UTC](https://forums.docker.com/t/docker-with-devicemapper-doesnt-start-on-centos-7/9641 "2016-04-20T14:59:35Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![vassellerie](https://avatars.discourse-cdn.com/v4/letter/v/74df32/32.png) [@vassellerie](https://forums.docker.com/u/vassellerie)\
**Post date:** [April 20, 2016, 2:59pm UTC](https://forums.docker.com/t/docker-with-devicemapper-doesnt-start-on-centos-7/9641/1 "2016-04-20T14:59:35Z")

</div>

Hello,

I’m facing an issue with Docker 1.9.1 under CentOS 7. I cannot start the docker daemon because it fails to set up the storage.  
This server worked for more than a year using the devicemapper on the same disk as the system (this is a test server so I didn’t define any specific storage). But now, when it starts, docker-storage-setup want to create a logical volume on the same volume group as the system, and of course there no more space available. I don’t understand why it can no more use the same storage under /var/lib/docker as it did until now. In addition there’s still some disk space available in /var/lib/docker.

Here are some details:

```
# /usr/bin/docker-storage-setup
  Rounding up size to full physical extent 24.00 MiB
  Volume group "system" has insufficient free space (1 extents): 6 required.

```

(this is normal as the VG system is using the whole disk space)

```
# df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/mapper/system-vg00 23049220 12779416 10269804 56% /
devtmpfs 1930828 0 1930828 0% /dev
tmpfs 1941412 0 1941412 0% /dev/shm
tmpfs 1941412 8668 1932744 1% /run
tmpfs 1941412 0 1941412 0% /sys/fs/cgroup
/dev/sda1 1002316 267456 682280 29% /boot
tmpfs 388284 0 388284 0% /run/user/1000

```

(as you see there still some disk space available for /var/lib/docker)

```
# cat /etc/sysconfig/docker-storage
DOCKER_STORAGE_OPTIONS=

```

(and nothing tells docker to use a new logical volume)

Any idea why this appeared ?

Thanks for your attention,

Regards,  
Pierre