# Unable to use "docker cp", but it worked 2 days ago **URL:** \ **Category:** Build Environment\ **Tags:** docker\ **Created:** [December 15, 2015, 6:48pm UTC](https://discuss.circleci.com/t/unable-to-use-docker-cp-but-it-worked-2-days-ago/1137 "2015-12-15T18:48:12Z")\ **Posts on this page:** 14\ **Page:** 1
**Author:** ![Alino](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/alino/32/751_2.png) [@Alino](https://discuss.circleci.com/u/Alino)\ **Post date:** [December 15, 2015, 6:48pm UTC](https://discuss.circleci.com/t/unable-to-use-docker-cp-but-it-worked-2-days-ago/1137/1 "2015-12-15T18:48:12Z")
```auto ubuntu@box723:~/kukni.to$ docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES a6b4d1a8bc93 kuknito/mongo2es "/bin/sh -c 'bash $ME" 12 minutes ago Up 12 minutes 0.0.0.0:3001->80/tcp Mongo2ES a6fb48610577 kuknito:elasticsearch "bin/elasticsearch" 12 minutes ago Up 12 minutes 0.0.0.0:9200->9200/tcp, 0.0.0.0:9300->9300/tcp ElasticSearch 7b20b7903447 mongo:3.0 "/entrypoint.sh mongo" 12 minutes ago Up 12 minutes 27017/tcp, 0.0.0.0:27018->27018/tcp MongoDB ubuntu@box723:~/kukni.to$ docker cp scripts/masterCategories.json MongoDB:/data/masterCategories.json Error response from daemon: permission denied ``` was something changed regarding docker recently? _docker cp_ used to work just 2 days ago, now when I rerun the same build where it worked, it no longer works and gives the error above. ---
**Author:** ![Alino](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/alino/32/751_2.png) [@Alino](https://discuss.circleci.com/u/Alino)\ **Post date:** [December 15, 2015, 7:03pm UTC](https://discuss.circleci.com/t/unable-to-use-docker-cp-but-it-worked-2-days-ago/1137/2 "2015-12-15T19:03:32Z")
my temporary solution until this is fixed is creating the file in the container like this: `sudo lxc-attach -n "$(docker inspect --format '{{.Id}}' MongoDB)" -- bash -c "cat > /data/masterCategories.json" < scripts/masterCategories.json` ---
**Author:** ![klingerf](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/klingerf/32/757_2.png) [@klingerf](https://discuss.circleci.com/u/klingerf)\ **Post date:** [December 15, 2015, 9:37pm UTC](https://discuss.circleci.com/t/unable-to-use-docker-cp-but-it-worked-2-days-ago/1137/3 "2015-12-15T21:37:37Z")
Am having the exact same problem. `docker cp` was working in our CI jobs yesterday, stopped work in all of our builds / branches this morning. From a recent run: ```auto + docker cp hosted-build-web:/go/bin/web /tmp/hosted-build-web/bin/ Error response from daemon: permission denied ``` It’s worth noting that we install our own version of docker / docker-machine using the following machine config in circle.yml: ```auto machine: pre: - sudo curl -L -o /usr/bin/docker 'https://s3-external-1.amazonaws.com/circle-downloads/docker-1.9.1-circleci' - sudo chmod 0755 /usr/bin/docker - sudo curl -o /usr/local/bin/docker-compose -L https://github.com/docker/compose/releases/download/1.5.1/docker-compose-`uname -s`-`uname -m` - sudo chmod +x /usr/local/bin/docker-compose ``` Have also tried upgrading those versions to latest to no avail. ---
**Author:** ![Alino](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/alino/32/751_2.png) [@Alino](https://discuss.circleci.com/u/Alino)\ **Post date:** [December 15, 2015, 9:54pm UTC](https://discuss.circleci.com/t/unable-to-use-docker-cp-but-it-worked-2-days-ago/1137/4 "2015-12-15T21:54:00Z")
I use the default docker version provided by circleCI. I couldn’t see anything about docker in recent changes in circle’s changelog. I created a support request for this with link to this thread. Hopefully it will get fixed soon. ---
**Author:** ![levlaz](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/levlaz/32/36978_2.png) [@levlaz](https://discuss.circleci.com/u/levlaz)\ **Post date:** [December 16, 2015, 1:26am UTC](https://discuss.circleci.com/t/unable-to-use-docker-cp-but-it-worked-2-days-ago/1137/5 "2015-12-16T01:26:18Z")
> [@Alino](#): > > sudo lxc-attach -n “$(docker inspect --format ‘{{.Id}}’ MongoDB)” – bash -c “cat \> /data/masterCategories.json” \< scripts/masterCategories.json Does this workaround work for you as well? ---
**Author:** ![levlaz](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/levlaz/32/36978_2.png) [@levlaz](https://discuss.circleci.com/u/levlaz)\ **Post date:** [December 16, 2015, 1:27am UTC](https://discuss.circleci.com/t/unable-to-use-docker-cp-but-it-worked-2-days-ago/1137/6 "2015-12-16T01:27:33Z")
Thank you for reporting this issue. Due to some security concerns we had to upgrade the version of LXC that runs on our builder boxes. It looks like this has broken `docker cp` our Engineers are looking into the cause of the issue and hope to have a resolution soon. In the meantime it looks like the workaround posted by @Alino should work: ```auto sudo lxc-attach -n "$(docker inspect --format '{{.Id}}' MongoDB)" -- bash -c "cat > /data/masterCategories.json" < scripts/masterCategories.json Reply ``` ---
**Author:** ![Alino](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/alino/32/751_2.png) [@Alino](https://discuss.circleci.com/u/Alino)\ **Post date:** [December 16, 2015, 9:47am UTC](https://discuss.circleci.com/t/unable-to-use-docker-cp-but-it-worked-2-days-ago/1137/7 "2015-12-16T09:47:15Z")
I don’t think it will work for @klingerf , my workaround is very limited to a single text file, copying from host to docker container, and klingerf seems that he wants to copy whole directory from docker container to host. ---
**Author:** ![kimh](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/kimh/32/19_2.png) [@kimh](https://discuss.circleci.com/u/kimh)\ **Post date:** [December 16, 2015, 10:50am UTC](https://discuss.circleci.com/t/unable-to-use-docker-cp-but-it-worked-2-days-ago/1137/8 "2015-12-16T10:50:50Z")
**[Updated 17th Dec]** I just patched docker and pushed to our public download site. It looks `docker cp` is working now. To use the patched version, you can put the following in your circle.yml. Please make sure to replace ``. Available versions: `1.8.2` `1.8.3` `1.9.0` `1.9.1` ```auto machine: pre: - echo 'DOCKER_OPTS="-s btrfs -e lxc -D --userland-proxy=false"' | sudo tee -a /etc/default/docker - sudo curl -L -o /usr/bin/docker 'https://s3-external-1.amazonaws.com/circle-downloads/docker--circleci-cp-workaround' - sudo chmod 0755 /usr/bin/docker services: - docker ``` Please report us if you find any problems. ---
**Author:** ![klingerf](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/klingerf/32/757_2.png) [@klingerf](https://discuss.circleci.com/u/klingerf)\ **Post date:** [December 16, 2015, 5:21pm UTC](https://discuss.circleci.com/t/unable-to-use-docker-cp-but-it-worked-2-days-ago/1137/9 "2015-12-16T17:21:15Z")
@kimh Thank you for providing the patched version! It doesn’t work for our build unfortunately because our setup uses docker-compose 1.5, which requires docker \>= 1.9. Any chance you can also provide a patched version of 1.9.1, which was introduced in this thread: > [@Docker 1.9.1 is available](https://discuss.circleci.com/t/docker-1-9-1-is-available/1009): > > We now have Docker 1.9.1 that runs on CircleCI. To use it, you can add the following to your circle.yml. This version has not been tested yet on CircleCI, so please use it with a care. Any bug/issue reports are welcome! machine: pre: - sudo curl -L -o /usr/bin/docker 'https://s3-external-1.amazonaws.com/circle-downloads/docker-1.9.1-circleci' - sudo chmod 0755 /usr/bin/docker services: - docker ​ Alternatively, I can look into a solution similar to the one @Alino provided. We might be able to use tar or another utility to get the files out of the container. ---
**Author:** ![kimh](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/kimh/32/19_2.png) [@kimh](https://discuss.circleci.com/u/kimh)\ **Post date:** [December 17, 2015, 1:20am UTC](https://discuss.circleci.com/t/unable-to-use-docker-cp-but-it-worked-2-days-ago/1137/10 "2015-12-17T01:20:12Z")
@klingerf Just patched 1.9 as well. Does 1.9 work for you? I need a bit more time to do 1.9.1, but will be done in a few hours. ```auto machine: pre: - echo 'DOCKER_OPTS="-s btrfs -e lxc -D --userland-proxy=false"' | sudo tee -a /etc/default/docker - sudo curl -L -o /usr/bin/docker 'https://s3-external-1.amazonaws.com/circle-downloads/docker-1.9.0-circleci-cp-workaround' - sudo chmod 0755 /usr/bin/docker services: - docker ``` ---
**Author:** ![klingerf](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/klingerf/32/757_2.png) [@klingerf](https://discuss.circleci.com/u/klingerf)\ **Post date:** [December 17, 2015, 1:53am UTC](https://discuss.circleci.com/t/unable-to-use-docker-cp-but-it-worked-2-days-ago/1137/11 "2015-12-17T01:53:10Z")
Hi @kimh – the patched version you provided fixes my issue. Thanks for all of your help with this! ---
**Author:** ![kimh](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/kimh/32/19_2.png) [@kimh](https://discuss.circleci.com/u/kimh)\ **Post date:** [December 17, 2015, 3:28am UTC](https://discuss.circleci.com/t/unable-to-use-docker-cp-but-it-worked-2-days-ago/1137/12 "2015-12-17T03:28:41Z")
@klingerf Patched and uploaded 1.9.1 as well. ---
**Author:** ![kazuhisya](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/kazuhisya/32/788_2.png) [@kazuhisya](https://discuss.circleci.com/u/kazuhisya)\ **Post date:** [December 17, 2015, 7:22pm UTC](https://discuss.circleci.com/t/unable-to-use-docker-cp-but-it-worked-2-days-ago/1137/13 "2015-12-17T19:22:02Z")
Hi @kimh Thank you for the great news. I had the same problem, then `docker-1.9.0-circleci-cp-workaround` worked well for me. ---
**Author:** ![system](https://global.discourse-cdn.com/circleci/original/3X/5/1/511608acda8e85906e15909b57bd0a46c1dbe291.png) [@system](https://discuss.circleci.com/u/system)\ **Post date:** [June 18, 2018, 11:37am UTC](https://discuss.circleci.com/t/unable-to-use-docker-cp-but-it-worked-2-days-ago/1137/14 "2018-06-18T11:37:48Z")