Your Docker installation is not using a supported storage driver

(Martial) #1

First bug : When i want to upgrade from the GUI the button always showing : “Currently Upgrading” but nothing append on the server side. I need to connect with ssh on the vps to rebuild the app manually. This is not the first time since i’m on 1.8.

Second bug :

Now when i try : rebuild app I have this message. I never have this problem before…

root@:/var/discourse# ./launcher rebuild app
Your Docker installation is not using a supported storage driver.  If we were to proceed you may have a broken install.
aufs is the recommended storage driver, although zfs/btrfs/overlay and overlay2 may work as well.
Other storage drivers are known to be problematic.
You can tell what filesystem you are using by running "docker info" and looking at the 'Storage Driver' line.

If you wish to continue anyway using your existing unsupported storage driver,
read the source code of launcher and figure out how to bypass this check.
root@:/var/discourse# docker info
Containers: 1
Images: 11
Server Version: 1.9.1
Storage Driver: devicemapper
 Pool Name: docker-253:1-247218-pool
 Pool Blocksize: 65.54 kB
 Base Device Size: 107.4 GB
 Backing Filesystem:
 Data file: /dev/loop0
 Metadata file: /dev/loop1
 Data Space Used: 5.234 GB
 Data Space Total: 107.4 GB
 Data Space Available: 7.431 GB
 Metadata Space Used: 4.346 MB
 Metadata Space Total: 2.147 GB
 Metadata Space Available: 2.143 GB
 Udev Sync Supported: false
 Deferred Removal Enabled: false
 Deferred Deletion Enabled: false
 Deferred Deleted Device Count: 0
 Data loop file: /var/lib/docker/devicemapper/devicemapper/data
 Metadata loop file: /var/lib/docker/devicemapper/devicemapper/metadata
 Library Version: 1.02.82-git (2013-10-04)
Execution Driver: native-0.2
Logging Driver: json-file
Kernel Version: 3.19.0-22-generic
Operating System: Ubuntu 15.04
CPUs: 1
Total Memory: 3.766 GiB
WARNING: No swap limit support

(Jeff Atwood) #2

Devicemapper is bad news; you will need to fix that.

(Matt Palmer) #3

See the previous discussion for more details.