The builds are broken on Docker 1.10.2

[mfojtik]

When using the latest Docker (note: installed from docker.org yum repos, not official centos repos), both S2I and Docker builds will fail with this error:

Docker build:

 ---> Running in 3ce1ba9b6292
builder.go:204] Error: build error: Cannot start container 3ce1ba9b6292ff467d1e9bb1ceb8923d7d4a80f17e295b7fa306c7a2eff80c7b: [9] System error: write /sys/fs/cgroup/memory/docker/3ce1ba9b6292ff467d1e9bb1ceb8923d7d4a80f17e295b7fa306c7a2eff80c7b/memory.limit_in_bytes: invalid argument

S2I build:

install.go:236] Using "save-artifacts" installed from "image:///usr/libexec/s2i/save-artifacts"
builder.go:204] Error: build error: API error (500): Cannot start container ea7c76f432b8a704843535c09c77c1598688b96ad1b07a641d6bd4b96a178566: [9] System error: write /sys/fs/cgroup/memory/docker/ea7c76f432b8a704843535c09c77c1598688b96ad1b07a641d6bd4b96a178566/memory.limit_in_bytes: invalid argument

Dunno if this is due to cgroup changes we did or something is badly broken in latest docker.
Keep in mind that this is probably low prio because I don't think we are getting 1.10.2 docker anytime soon, but we should keep eyes on this.

EDIT: This was done on centos7.1.

[mfojtik]

@bparees @smarterclayton FYI

[mfojtik]

also it might be possible that there is something missing here: https://docs.docker.com/engine/installation/linux/centos/

[smarterclayton]

Well, we need to fix it in case anyone tries to upgrade to 1.10.2 in the open source community, or if it points to a bug in our cgroup handling. Giving it p1 to triage.

[mfojtik]

@vbatts any clues about what can be configured wrong for docker? The systemd service installed by that evil script from docker seems to just run docker -H fd:// without any other additional parameters. I wonder if something has to be setup before you want to use CGroups.

[mfojtik]

FYI: moby/moby#20603 (comment)

[dbalakirev]

@mfojtik so as wrote in that ticket I happen to have this issue. But with RHEL 7.2 and of course docker engine 1.10.2.

[mfojtik]

@dbalakirev I can reproduce it on centos7 with docker engine 1.10.2 :-)

[bparees]

this is one of the things I reported in #6822 (comment)

[bparees]

ok not exactly the same, very similar.

[bparees]

@mfojtik does this error occur if you simply run a raw "docker build" command on your host, passing the various limits via the docker build flags?