For the hell of it I deleted /var/lib/docker/devicemapper on the off change there is a packaging issue similar to https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1569763. No change.
There is a docker service running. It doesn't work (docker ps hangs); syslog says:
Apr 22 21:25:50 Nix systemd[1]: Started Docker Application Container Engine. Apr 22 21:25:50 Nix systemd[1]: Starting Docker Application Container Engine... Apr 22 21:25:50 Nix docker[11685]: time="2016-04-22T21:25:50.397372552-07:00" level=error msg="'overlay' not found as a supported filesystem on this host. Please ensure kernel is new enough and has overlay support loaded." Apr 22 21:25:50 Nix kernel: [ 3621.739895] device-mapper: table: 252:0: thin-pool: unknown target type Apr 22 21:25:50 Nix kernel: [ 3621.739899] device-mapper: ioctl: error adding target to table
Anyway -- Recent Macbook Pro, VirtualBox 5.0.16, Ubuntu 16.04 desktop ISO, sudo apt install docker.io
It looks more and more like a ubuntu apt/systemd oops than a docker specific problem.
For the hell of it I deleted /var/lib/ docker/ devicemapper on the off change there is a packaging issue similar to https:/ /bugs.launchpad .net/ubuntu/ +source/ docker. io/+bug/ 1569763. No change.
There is a docker service running. It doesn't work (docker ps hangs); syslog says:
Apr 22 21:25:50 Nix systemd[1]: Started Docker Application Container Engine. 04-22T21: 25:50.397372552 -07:00" level=error msg="'overlay' not found as a supported filesystem on this host. Please ensure kernel is new enough and has overlay support loaded."
Apr 22 21:25:50 Nix systemd[1]: Starting Docker Application Container Engine...
Apr 22 21:25:50 Nix docker[11685]: time="2016-
Apr 22 21:25:50 Nix kernel: [ 3621.739895] device-mapper: table: 252:0: thin-pool: unknown target type
Apr 22 21:25:50 Nix kernel: [ 3621.739899] device-mapper: ioctl: error adding target to table
Anyway -- Recent Macbook Pro, VirtualBox 5.0.16, Ubuntu 16.04 desktop ISO, sudo apt install docker.io
It looks more and more like a ubuntu apt/systemd oops than a docker specific problem.