samba container: libdevmapper error on Arch

[nem75]

I have a project where I use Vagrant to fire up the docker containers, including a samba container created by svendowideit/samba. This used to work without flaw on Ubuntu.

After switching to Arch starting up the container which would create a samba container no longer does so but instead shows this in the log:

/docker: error while loading shared libraries: libdevmapper.so.1.02: cannot open shared object file: No such file or directory

I have no idea what to do with that.

A find for the module comes up with

/usr/lib/libdevmapper.so.1.02
/usr/lib/libdevmapper.so
/var/lib/docker/devicemapper/mnt/65aa816ef1b3a54563fd6ffcf3757795f7da8073453623dc273d0f10e907837b/rootfs/lib/x86_64-linux-gnu/libdevmapper.so.1.02.1
/var/lib/docker/devicemapper/mnt/c7e56b4e59fe6a93050c58b30d882071b7066cbc314d69fe9be804cd694589b8/rootfs/lib/x86_64-linux-gnu/libdevmapper.so.1.02.1
/var/lib/docker/devicemapper/mnt/387581c04489d2ffab36d9117903e33d6edac285a23bf96172e2f873e960c943/rootfs/lib/x86_64-linux-gnu/libdevmapper.so.1.02.1

The parameters running the samba container have not changed. The volume mappings

container.volumes = ["/usr/bin/docker:/docker", "/var/run/docker.sock:/docker.sock"]

still point to valid files in the host file system.

Anything else I can do to pinpoint the problem?

Edit: just tried it without Vagrant, same difference.

docker run --rm -v `which docker`:/docker -v /var/run/docker.sock:/docker.socker svendowideit/samba <name of the target container>

still results in

/docker: error while loading shared libraries: libdevmapper.so.1.02: cannot open shared object file: No such file or directory

Edit 2:

$ docker --version
Docker version 1.2.0, build fa7b24f

[ariddell]

Getting a similar problem with Docker 1.3.3 on coreos