Phil Porada

``` [root@365f17e65bac ~]# docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES aaa6d474da8c greenlancer/jenkins-slave:latest "/opt/entrypoint.sh" 31 minutes ago Up 30 minutes 0.0.0.0:32772->22/tcp evil_heisenberg fbf3e9051104 greenlancer/jenkins-slave:latest "/opt/entrypoint.sh" 31 minutes ago...

Here is one of the 5 identical containers that was spun up. I set the idle timeout of 15 minutes manually, yes. ``` [ { "Id": "aaa6d474da8cd141c77644e19a6ffc1cb59b2699c1666347eda3a47f4f7a783e", "Created": "2016-11-10T22:12:09.450765169Z", "Path":...

Ah, I gotcha. Do you have a location where I can see the Dockerfile for `kostyasha/jenkins-slave`

I'm going to call it a night for now. I will pick this fight with JNLP back up tomorrow. I can see the container launching which is a good thing....

Are you on Docker 1.12.x and do you have a systemd socket file in place? https://github.com/docker/docker/tree/master/contrib/init/systemd

Disregard my previous comment. I am running into the same issue. ``` YADP 0.1.0-rc29 ``` ``` [root@365f17e65bac ~]# docker version Client: Version: 1.12.3 API version: 1.24 Go version: go1.6.3 Git...

I was expecting this to work the same as the Docker Plugin where I had the SSH launcher working. However, that was on Docker 1.11.2 and the Docker Plugin failed...

Good point about the crc checks. I read the XFS man page entry for it, but all the examples I saw showed people disabling it. I guess that means do...

Ahhh, this is why CRC was set to 0. ``` + mkfs.xfs -m crc=1 -n ftype=1 -L root /dev/xvdb2 cannot specify both crc and ftype Usage: mkfs.xfs ```