# Collabora Docker capabilities problem

**URL:** <https://help.nextcloud.com/t/collabora-docker-capabilities-problem/4774>\
**Category:** ℹ️ Support\
**Created:** [November 3, 2016, 10:33am UTC](https://help.nextcloud.com/t/collabora-docker-capabilities-problem/4774 "2016-11-03T10:33:25Z")\
**Posts on this page:** 1\
**Showing post:** 14

<div class="post-metadata">

**Author:** ![Andreas\_Fuchs](https://help.nextcloud.com/letter_avatar/andreas_fuchs/32/6_22734026db12803ebb3e059622ac3534.png) [@Andreas\_Fuchs](https://help.nextcloud.com/u/Andreas_Fuchs)\
**Post date:** [December 15, 2016, 11:04am UTC](https://help.nextcloud.com/t/collabora-docker-capabilities-problem/4774/14 "2016-12-15T11:04:05Z")

</div>

Thanks @GuZ your tip helped me solve the issue on Ubuntu 14.04

I stopped the clloabora dock by

```
docker ps (to get the id)
docker stop [id]
docker rm [id]

```

then changed _/etc/default/docker_

```
# Use DOCKER_OPTS to modify the daemon startup options.
DOCKER_OPTS="--storage-driver=devicemapper"

```

restarted docker  
and started collabora again which downloaded a new image and is running perfect now

for big production sites it’s maybe worth do fix the aufs problem or to propperly configure devicemapper like described here: [https://docs.docker.com/engine/userguide/storagedriver/device-mapper-driver/](https://docs.docker.com/engine/userguide/storagedriver/device-mapper-driver/), for personal use about fix should be fine

---

_[View the full topic](https://help.nextcloud.com/t/collabora-docker-capabilities-problem/4774)._