`docker cp -a` docs incorrect

Open Beginner friendly
#17,533 23 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
62/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Active
Tech stack
docker
Domain
documentation

Research direction

Open the Docker CLI cp documentation at the linked command-line reference and inspect the description of -a. Reproduce the reported docker cp behavior with and without -a, then update the archive-mode wording to match the verified behavior; done means the documentation no longer makes the incorrect ownership claim.

Written by the indexing model from the issue text.

Description

agent/skip agent/triaged area/engine status/triage
Is this a docs issue?
  • My issue is about the documentation content or website
Type of issue

Information is incorrect

Description

Docs for docker cp -a claim that -a will "Archive mode (copy all uid/gid information)"

My testing shows that this is incorrect.

It appears that docker cp . container-name:/ without the -a flag will preserve ownership of the copied files. That is, a file owned by user ID 1234 on the host will be created with user ID 1234 within the container.

Adding the -a flag will instead change the ownership of copied files to match the --user of the container.

Location

https://docs.docker.com/engine/reference/commandline/cp/

Suggestion

No response

Dominant language
Markdown
Stars
4.7k
Forks
8.5k
Avg merge
2d 16h
Merged PRs (30d)
107

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from docker/docs

All issues in docker/docs

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.