This happens whether contents is a directory or a file. For example, if the container contains /tmp/testdir/contents and /tmp/testdir is mode 555, then contents will not be copied. Commands like docker inspect test and docker rm test hangs forever. Using docker cp to copy a directory from a container to the host fails when creating contents if the directory is read-only.Run docker cp test test:/tmp, and press Ctrl-C while this command is still running.Create a directory test with big files inside.Run docker create -name test busybox or docker run -rm -name test -it busybox sh.Reproducible: Yes, on my two MacBook Pros.When I tried to copy a symbol link into a docker container, I found that the docker cp cant follow the symbol link and only copied an invalid symbol file. Add option -L to allow docker cp follow symbol link WeiZhang555/moby. I tried to call PUT /containers//archive directed on the Unix socket, getting the same result.Ī restart on Docker Desktop will fix this, but it's troubling. Successfully merging a pull request may close this issue. Any command on this container fails, including docker inspect.

Actual behaviorĪfter a docker cp (from host to container) command is interrupted, the container is seemly in deadlock. Corrupted files may be in the container but are acceptable. Diagnostics ID: 6671EC64-8D5A-4A5F-91CD-55DC396A8FCD/20200426084429Īfter a docker cp (from host to container) command is interrupted (such as by Ctrl-C), the container should functions normally.I have tried with the latest version of my channel (Stable or Edge).

Docker cp