Docker in Slackware 14.2 stable: error initializing graphdriver: Error running DeviceCreate (CreatePool) dm_task_run failed
 

I just installed Docker 1.8.2 from SBo https://slackbuilds.org/repository/1...?search=docker in Slackware 14.2 Stable but when I try to start the daemon I get:

docker daemon -D gives:
check-config.sh gives:
I tried many things like running with --storage-opt="dm.blocksize=64k" or removing /var/lib/docker but nothing seems to work.

Any idea is much appreciated.

Did you create the "docker" group? Did you add yourself to the "docker" group?

I ran the command "groupadd -r -g 281 docker" as root prior to installing docker.

try this: http://www.linuxquestions.org/questi...2/#post5520986

i just updated to 14.2 and i think its no longer an issue but it might be my original fix is still in place. there are 2 ways to handle it:

1) recompile the kernel with the following:
Device Drivers
-> Multiple devices driver support (RAID and LVM)
---> Device mapper support [M]

2) or use the non-huge kernel that uses modules

FYI, docker works fine here on a stock slackware64-14.2 (32bit installs are not supported).

what I have done:
- installed google-go-lang from SBo (it has some files in /etc/profile.d that must be loaded so after installing it you have to logout/reboot);
- created the docker group as written in the docker's README on SBo and added my user to it (to be effective you have to logout/login again);
- rebooted my host for the above stuff to be effective;
- installed docker from SBo;
- launched the daemon
- executed a shell in a docker container as a user
no issues at all with the device mapper

I just did the same in a new Slackware 14.2 64bits inside a VBox VM and nothing:

I used the Kernel Huge and Ext4.

Any other difference that might cause this error?

I'm using the generic kernel here.

I'm blind guessing: have you tried doing this not inside a virtual machine but on a real host?

Sadly the devicemapper output is not always helpful.

It is worth confirming the behavior on your machine the generic kernel as well (you'll need to make an initrd). I do not have this issue, and I also use the generic kernel.

Further, there are other storage drivers for Docker that I feel work better. I personally prefer btrfs. It requires making a partition mkfs.btrfs formatted partition mounted at /var/lib/docker. Overlayfs is also good, but has a couple edge cases that are less than ideal.

Why do you believe that btrfs is a better storage driver for Docker than ext4?

I'm not claiming that it isn't; I'm curious what features btrfs provides that makes it better.

This isn't a comparison to ext4, it is a comparison to the docker devicemapper storage driver (https://github.com/docker/docker/tre...iver/devmapper).
A docker feature that is hidden in generic usage, when it defaults to using the 'devicemapper' storagedriver.
If you haven't manually created an lvm thinpool blocked device and configured docker's devicemapper driver to use it, then the driver defaults to creating flat files that it attaches to a loopback block device, and then uses these.
There are a number of moving parts, and in this most generic, default behavior, the performance is not great. At all.

As for the other storage drivers, none of them are "a clear winner".
'btrfs' is performant. But eventually folks say that after a while it slows a bit. Sometime ago the kernel's btrfs had issues (like a btree cksum corruption). Honestly I like it though, and haven't had much issues.
'overlay' - is great, but has edgecases. It's not technically POSIX compliant. The underlying FS ought to be ext4 or xfs. It handles unix sockets not straight-forward (due to opening it for a write causes a copy-up). There are behavior's about opening files for read, and while still holding the file-handle, when another file-handle is opened for write. Now you have open file-handles for two different inodes.
'aufs' - is only for ubuntu, and requires carried kernel-patches. Don't use this.
'zfs' - i hear good things. never used it. the zfs modules can be compiled and used without patching your kernel
'devicemapper' - it is enterpris'ie, but requires some hands on knowledge and management in-order to have a good experience.

Ah. Thanks for the detailed answer. I'll have to play with my setup when I get home. :)

Yep. Docker works fine in Slackware 14.2 with Generic Kernel not with Huge Kernel.

For those like me who did not bother to use Generic Kernel you can get some info on how to use Generic Kernel here

Thanks for all the replies.

Hi glands
Just for recording, I have the same scenario Slackware 14.2 64bits inside a VBox VM and has another way to make docker run by editing the file /etc/default/docker, adding the next line:

# Force OverlayFS for storage driver
DOCKER_OPTS="$DOCKER_OPTS -s overlay"

http://stackoverflow.com/questions/3...g-on-this-host