You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
$ docker run --rm mesosphere/mesos-slave-dind:0.2.1_mesos-0.23.0_docker-1.8.2_ubuntu-14.04.2
/dev/mapper/control: open failed: Operation not permitted
Failure to communicate with kernel device-mapper driver.
Check that device-mapper is available in the kernel.
Command failed
mount: permission denied
Could not mount /sys/kernel/security.
AppArmor detection and --privileged mode might break.
0+0 records in
0+0 records out
0 bytes (0 B) copied, 5.6115e-05 s, 0.0 kB/s
mke2fs 1.42.9 (4-Feb-2014)
/data/docker is not a block special device.
Proceed anyway? (y,n) Discarding device blocks: done
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
327680 inodes, 1310720 blocks
65536 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=1342177280
40 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736
Allocating group tables: done
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done
mount: Could not find any loop device. Maybe this kernel does not know
about the loop device? (If so, recompile or `modprobe loop'.)
add bridge failed: Operation not permitted
bridge docker0 does not exist!
Cannot find device "docker0"
RTNETLINK answers: Operation not permitted
Cannot find device "docker0"
Cannot find device "docker0"
Using network 0.0.1.0/24 for docker containers
time="2015-10-17T01:50:14.972501676Z" level=info msg="Listening for HTTP on unix (/var/run/docker.sock)"
time="2015-10-17T01:50:15.106695536Z" level=error msg="'overlay' is not supported over aufs."
time="2015-10-17T01:50:15.106968262Z" level=fatal msg="Error starting daemon: error initializing graphdriver: backing file system is unsupported for this graph driver"
I had to disable the set -e otherwise it explodes early.
The text was updated successfully, but these errors were encountered:
On my local boot2docker:
I had to disable the
set -e
otherwise it explodes early.The text was updated successfully, but these errors were encountered: