Docker 1.10.0 is available (Beta)

@kimh any updates on docker 1.10 and caching?

@alikhan_io No solid update for caching so far. I don’t have a good solution now, so just waiting for some update at https://github.com/docker/docker/issues/20380 and https://github.com/docker/docker/issues/20451

@kimh Any updates on docker exec?

1 Like

@VikParuchuri Sorry, not real update either for docker exec. Unlike docker cp issue, it’s just I couldn’t take time on this, though. I’ll give you an update sometime in this week.

Is it possible to install docker-compose 1.6 also?

We have been manually pip installing docker-compose==1.6.0 in test:pre. Seems to work fine. Everything working except as reported above; no caching, copy, or exec.

1 Like

Thanks! I’ll look into that.

We’re having the same issue with Docker exec. We’re trying to get out current Docker build process working in Circle CI, and this is a deal breaker for us.

1 Like

I had issues with pip so I went another direction to install docker-compose with:

dependencies:
  override:
    - curl -L https://github.com/docker/compose/releases/download/1.6.2/docker-compose-`uname -s`-`uname -m` > ~/docker-compose
    - chmod +x ~/docker-compose
    - ~/docker-compose version

Are there any updates on supporting docker exec? I’m still getting the error:

open /proc/self/oom_score_adj: no such file or directory

Any workarounds? Would love this feature.

sudo lxc-attach -n "$(docker inspect --format '' $MY_CONTAINER_NAME)" -- bash -c $MY_COMMAND

See bottom of https://circleci.com/docs/docker/

Any updates? It looks like https://github.com/docker/docker/issues/20451 is closed but https://github.com/docker/docker/issues/20380 is still open.

Caching via load/save will be fixed in 1.11 See: https://github.com/docker/docker/pull/21385

1 Like

I’m having issues with both docker exec and lxc-attach with the 1.10 build.

~$ docker --version
Docker version 1.10.0-circleci, build 543ec7b-unsupported
~$ docker exec -it postgres pg_isready
open /proc/self/oom_score_adj: no such file or directory
~$ sudo lxc-attach -n "$(docker inspect --format '{{.Id}}' postgres)" -- bash -c "pg_isready"
lxc-attach: attach.c: lxc_attach: 710 failed to get the init pid
3 Likes

Doesn’t work for me either. This is probably why 1.10 is “beta”. Personally, I’m using a workaround where I mount a shell script and run it on the container run:

docker run -it \
  -v /my/script.sh:/usr/sbin/myscript \
  my-image sh -c "myscript && ..."

1.11 is out. Can we please get support if only to try caching again? This discussion has been started here:

https://discuss.circleci.com/t/requesting-docker-1-11/3346

1 Like

+1 for 1.11 support.

3 Likes

After some monkeying around here is some important information:

  • lxc-attach can’t work with any versions of docker 1.10 or above as the lxc driver has been removed completely now (it’s not even an option anymore). See https://github.com/docker/docker/releases/tag/v1.10.0
  • The default docker version right now on circleCI is 1.8.3.
  • The documentation for using lxc-attach is broken… it’s missing the --format='{{.Id}}' See https://circleci.com/docs/docker/#docker-exec which just shows --format=''.
  • lxc-attach is NOT a proper replacement for docker exec as all of the usual docker environment variables are missing, the login directory will be / instead of your WORKDIR, you can’t see all the running processes, etc.
  • also tried to see if docker-in-docker would work, but looks like that’s broken as well. docker run --privileged --name some-docker -d docker:1.11-dind gave warnings, then the container never started.

I can’t even get as far as finding out that push/pull don’t work. I simply get:

Starting docker
start: Job failed to start
service docker start returned exit code 1
Action failed: Starting docker

I’d like to bump this thread as well. Docker exec is a pretty important feature to my organization.