Arch Linux

tikiking1

Member

Registered: 2014-01-24

Posts: 12

[SOLVED] docker + LUKS

I've been using docker for a while now, and have installed it on my laptop so that I can get stuff done during lectures. However, it seems to not work at all on the laptop. Just booting, there are no problems, but when I issue as simple a command as `sudo docker version`, I get:

Client version: 1.2.0
Client API version: 1.14
Go version (client): go1.3.1
Git commit (client): fa7b24f
OS/Arch (client): linux/amd64
2014/09/20 17:19:13 Get http:///var/run/docker.sock/v1.14/version: read unix /var/run/docker.sock: connection reset by peer

Running the command again gets:

Client version: 1.2.0
Client API version: 1.14
Go version (client): go1.3.1
Git commit (client): fa7b24f
OS/Arch (client): linux/amd64
2014/09/20 17:27:52 Cannot connect to the Docker daemon. Is 'docker -d' running on this host?

I am using LUKS (but not LVM), so I figure this could be part of the problem.

dmesg outputs:

[   95.292917] loop: module loaded
[   95.298500] device-mapper: table: 254:2: thin-pool: unknown target type
[   95.298506] device-mapper: ioctl: error adding target to table
[   95.319192] device-mapper: table: 254:2: thin-pool: unknown target type
[   95.319197] device-mapper: ioctl: error adding target to table
[   95.339438] device-mapper: table: 254:2: thin-pool: unknown target type
[   95.339444] device-mapper: ioctl: error adding target to table
[   95.359887] device-mapper: table: 254:2: thin-pool: unknown target type
[   95.359893] device-mapper: ioctl: error adding target to table
[   95.384141] device-mapper: table: 254:2: thin-pool: unknown target type
[   95.384145] device-mapper: ioctl: error adding target to table

`sudo systemctl status docker`:

Sep 20 17:19:13 Surfactant systemd[1]: Started Docker Application Container Engine.
Sep 20 17:19:13 Surfactant docker[545]: 2014/09/20 17:19:13 docker daemon: 1.2.0 fa7b24f; execdriver: native; graphdriver:
Sep 20 17:19:13 Surfactant docker[545]: [6ca804d9] +job serveapi(fd://)
Sep 20 17:19:13 Surfactant docker[545]: [info] Listening for HTTP on fd ()
Sep 20 17:19:13 Surfactant docker[545]: 2014/09/20 17:19:13 Error running DeviceCreate (createPool) dm_task_run failed
Sep 20 17:19:13 Surfactant systemd[1]: docker.service: main process exited, code=exited, status=1/FAILURE
Sep 20 17:19:13 Surfactant systemd[1]: Unit docker.service entered failed state.
Sep 20 17:19:13 Surfactant systemd[1]: Starting Docker Application Container Engine...
Sep 20 17:19:13 Surfactant systemd[1]: docker.service start request repeated too quickly, refusing to start.
Sep 20 17:19:13 Surfactant systemd[1]: Failed to start Docker Application Container Engine.

Last edited by tikiking1 (2014-09-21 07:25:22)

firecat53

Member

From: Lake Stevens, WA, USA

Registered: 2007-05-14

Posts: 1,542

Website

Re: [SOLVED] docker + LUKS

I'm running Docker on my Luks encrypted laptop with Btrfs and have no issues. Try:

1. Remove /var/lib/docker and restart the daemon.
2. Disable the systemd service and start the docker daemon manually to see what happens

Scott

---

Github

tikiking1

Member

Registered: 2014-01-24

Posts: 12

Re: [SOLVED] docker + LUKS

Thanks, but neither of those seem to have worked.

I just realised that I should have mentioned that I'm using linux-ck, with BFQ.

Last edited by tikiking1 (2014-09-21 00:09:23)

tikiking1

Member

Registered: 2014-01-24

Posts: 12

Re: [SOLVED] docker + LUKS

I found the issue; I had originally compiled linux-ck with

_localmodcfg=y

Although this does make the compile much quicker, it also means that I can't modprobe anything that wasn't already probed at kernel compile time.