title: cannot start docker daemon (graphdriver issue)
body: <p>running <strong>Ubuntu 16.04.5 LTS 4.4.0-108-generic</strong> on a virtual private server 
  My aim is to deploy a meteor application with mup.js,
  but it fails because of dockerd not being launched. The problem is, i cannot get dockerd to launch after a system reboot.</p>
  
  <p>I tried changing graphdriver as suggested in other threads
  (<a href="https://stackoverflow.com/questions/45103803/not-able-to-start-docker-on-ubuntu-16-04-2-lts-error-initializing-graphdriver">Not able to start docker on Ubuntu 16.04.2 LTS (error initializing graphdriver)</a>), switching to aufs or overlay2, but to no avail. I also updated my kernel, purged docker repos, reinstalled docker on my machine.</p>
  
  <p>i have close to no experience working with docker, and the website i'm trying to put back online is part of a show, the last night of which is tomorrow! i must say i'm getting a bit desperate, any help is welcome.</p>
  
  <p>thank you!</p>
  
  <p>docker &amp; dockerd are both version <strong>18.06.1-ce, build e68fc7a</strong></p>
  
  <pre><code>$ sudo dockerd
  
  INFO[0000] libcontainerd: new containerd process, pid: 3488 
  WARN[0000] containerd: low RLIMIT_NOFILE changing to max  current=1024 max=1048576
  WARN[0000] failed to rename /var/lib/docker/tmp for background deletion: %!s(&lt;nil&gt;). Deleting synchronously 
  Error starting daemon: error initializing graphdriver: driver not supported
  </code></pre>
  
  <p>journalctl -xe yields :</p>
  
  <pre><code>Oct 03 01:22:19 vps332343 systemd[1]: Listening on Docker Socket for the API.
  -- Subject: Unit docker.socket has finished start-up
  -- Defined-By: systemd
  -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
  -- 
  -- Unit docker.socket has finished starting up.
  -- 
  -- The start-up result is done.
  Oct 03 01:22:19 vps332343 systemd[1]: docker.service: Start request repeated too quickly.
  Oct 03 01:22:19 vps332343 systemd[1]: Failed to start Docker Application Container Engine.
  -- Subject: Unit docker.service has failed
  -- Defined-By: systemd
  -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
  -- 
  -- Unit docker.service has failed.
  -- 
  -- The result is failed.
  Oct 03 01:22:19 vps332343 systemd[1]: docker.socket: Unit entered failed state.
  Oct 03 01:22:37 vps332343 sudo[3651]:  eboutin : TTY=pts/0 ; PWD=/etc/nginx/sites-available ; USER=root ; COMMAND=/bin/journalctl -xe
  Oct 03 01:22:37 vps332343 sudo[3651]: pam_unix(sudo:session): session opened for user root by eboutin(uid=0)
  </code></pre>
  
  <p>df -tH yields :</p>
  
  <pre><code>Filesystem     Type      Size  Used Avail Use% Mounted on
  udev           devtmpfs  970M     0  970M   0% /dev
  tmpfs          tmpfs     196M  5.6M  190M   3% /run
  /dev/vda1      ext4      9.7G  4.6G  5.1G  48% /
  copymods       tmpfs     977M   28K  977M   1% /lib/modules
  tmpfs          tmpfs     977M   68K  977M   1% /dev/shm
  tmpfs          tmpfs     5.0M     0  5.0M   0% /run/lock
  tmpfs          tmpfs     977M     0  977M   0% /sys/fs/cgroup
  tmpfs          tmpfs     196M     0  196M   0% /run/user/1002
  tmpfs          tmpfs     196M     0  196M   0% /run/user/1001
  </code></pre>
  
  <p>/etc/docker/daemon.json contents :</p>
  
  <pre><code>{"storage-driver":"devicemapper"}
  </code></pre>
  
  <p>(no other modified config file)</p>