Docker 1.10.0 is available (Beta)



Hi @mwolny following up your docker cp error. I’ve done a simple test but copy seems working for both direction (host -> container and container -> host).

My tests are running the following commands.

export n=test-cp && docker run --name $n ubuntu true && docker cp $n:/etc/hosts . && cat hosts
export n=test-cp && echo "hello" > hello.txt && docker cp hello.txt $n:/hello.txt

Do you have a command to reproduce the error?



Last login: Tue Feb 16 09:14:19 2016 from
(venv-2.7.6)ubuntu@box14:~$ docker run -it ubuntu bash
root@1027a705b092:/# apt-get install -y python
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
  libpython-stdlib libpython2.7-minimal libpython2.7-stdlib python-minimal
  python2.7 python2.7-minimal
Suggested packages:
  python-doc python-tk python2.7-doc binutils binfmt-support
The following NEW packages will be installed:
  libpython-stdlib libpython2.7-minimal libpython2.7-stdlib python
  python-minimal python2.7 python2.7-minimal
0 upgraded, 7 newly installed, 0 to remove and 0 not upgraded.
Need to get 3734 kB of archives.
After this operation, 16.0 MB of additional disk space will be used.
Get:1 trusty/main libpython2.7-minimal amd64 2.7.6-8 [307 kB]
Get:2 trusty/main python2.7-minimal amd64 2.7.6-8 [1190 kB]
Get:3 trusty/main libpython2.7-stdlib amd64 2.7.6-8 [1872 kB]
Get:4 trusty/main libpython-stdlib amd64 2.7.5-5ubuntu3 [7012 B]
Get:5 trusty/main python2.7 amd64 2.7.6-8 [197 kB]
Get:6 trusty/main python-minimal amd64 2.7.5-5ubuntu3 [27.5 kB]
Get:7 trusty/main python amd64 2.7.5-5ubuntu3 [134 kB]
Fetched 3734 kB in 0s (7042 kB/s)
E: Can not write log (Is /dev/pts mounted?) - openpty (2: No such file or directory)
Selecting previously unselected package libpython2.7-minimal:amd64.
(Reading database ... 11542 files and directories currently installed.)
Preparing to unpack .../libpython2.7-minimal_2.7.6-8_amd64.deb ...
Unpacking libpython2.7-minimal:amd64 (2.7.6-8) ...
Selecting previously unselected package python2.7-minimal.
Preparing to unpack .../python2.7-minimal_2.7.6-8_amd64.deb ...
Unpacking python2.7-minimal (2.7.6-8) ...
Selecting previously unselected package libpython2.7-stdlib:amd64.
Preparing to unpack .../libpython2.7-stdlib_2.7.6-8_amd64.deb ...
Unpacking libpython2.7-stdlib:amd64 (2.7.6-8) ...
Selecting previously unselected package libpython-stdlib:amd64.
Preparing to unpack .../libpython-stdlib_2.7.5-5ubuntu3_amd64.deb ...
Unpacking libpython-stdlib:amd64 (2.7.5-5ubuntu3) ...
Selecting previously unselected package python2.7.
Preparing to unpack .../python2.7_2.7.6-8_amd64.deb ...
Unpacking python2.7 (2.7.6-8) ...
Selecting previously unselected package python-minimal.
Preparing to unpack .../python-minimal_2.7.5-5ubuntu3_amd64.deb ...
Unpacking python-minimal (2.7.5-5ubuntu3) ...
Selecting previously unselected package python.
Preparing to unpack .../python_2.7.5-5ubuntu3_amd64.deb ...
Unpacking python (2.7.5-5ubuntu3) ...
Processing triggers for mime-support (3.54ubuntu1.1) ...
Setting up libpython2.7-minimal:amd64 (2.7.6-8) ...
Setting up python2.7-minimal (2.7.6-8) ...
Linking and byte-compiling packages for runtime python2.7...
Setting up libpython2.7-stdlib:amd64 (2.7.6-8) ...
Setting up libpython-stdlib:amd64 (2.7.5-5ubuntu3) ...
Setting up python2.7 (2.7.6-8) ...
Setting up python-minimal (2.7.5-5ubuntu3) ...
Setting up python (2.7.5-5ubuntu3) ...
root@1027a705b092:/# python -c "import pty; print pty.openpty()"
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/usr/lib/python2.7/", line 29, in openpty
    master_fd, slave_name = _open_terminal()
  File "/usr/lib/python2.7/", line 70, in _open_terminal
    raise os.error, 'out of pty devices'
OSError: out of pty devices


@eddwardo I think I fixed the pty issue. Can you try again now?

You can see it’s working at


@kimh pty opening works. How about cache now? Should I do it like this?

    - if [[ -e ~/docker/image.tar ]]; then docker load -i ~/docker/image.tar; fi
    - perl
    - docker build --build-arg CIRCLE_BUILD_NUM=$CIRCLE_BUILD_NUM -f Dockerfile-circleci -t env:latest .
    - mkdir -p ~/docker; docker save env:latest > ~/docker/image.tar 

If so, why caching doesn’t seem to work?


Thanks for the Beta!
We’ve tried this out on our builds and it works except for caching.

Our builds use the docker load/save ~/docker/image.tar idiom.
With docker 1.9, docker build uses cached layers from image.tar.
With docker 1.10 (beta), docker build executes all commands in the Dockerfile every time, regardless of cache.


Hi @pmbauer

It looks the caching does not work with load/save in 1.10. Please see the issue that I created.

There is an alternative way to use caching on CircleCI Caching Docker image with Docker Hub Maybe you can try this approach?

Caching Docker image with Docker Hub

Since you’re switching off of LXC, are there any plans to support docker exec with this release? I get this error when I run docker exec with the 1.10 docker beta:

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

Exit Code 255 on all Docker exec commands

@kimh Unfortunately, the docker pull approach (for using the docker cache) also no longer works with the 1.10 beta.


@VikParuchuri I also love docker exec to work. I’ll give it a try sometime this week.


@pmbauer You are right. docker pull doesn’t use cache either probably because of the same reason for docker load/save not working. Let me think what we can do here a bit.


Holy cow, and I tried everything all day to fix this cache thing, I should have checked the forum…

Regarding caching:

  • load/save does not work
  • pull/push does not work
  • pull base image then build does not work

I’m all out of options, hope you find a solution!


@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 and


@kimh Any updates on docker exec?


@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.


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.


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

    - curl -L`uname -s`-`uname -m` > ~/docker-compose
    - chmod +x ~/docker-compose
    - ~/docker-compose version