Debian installation pitfall
Maintainers usually reply within 1 day
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 85/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- docker, markdown
- Domain
- documentation
Research direction
Start with the Debian installation instructions at https://docs.docker.com/engine/install/debian/ and locate the listed apt install ca-certificates curl command. Check how the instructions behave on a fresh Debian 13 install, as suggested in the issue. Done means the installation steps no longer consume the next pasted line and complete without the reported keyring errors.
Written by the indexing model from the issue text.
Description
Is this a docs issue?
- My issue is about the documentation content or website
Type of issue
Information is incorrect
Description
If you copy+paste this part of the debian installation instructions on a relatively fresh Debian 13 install...
# Add Docker's official GPG key:
sudo apt update
sudo apt install ca-certificates curl
sudo install -m 0755 -d /etc/apt/keyrings
sudo curl -fsSL https://download.docker.com/linux/debian/gpg -o /etc/apt/keyrings/docker.asc
sudo chmod a+r /etc/apt/keyrings/docker.asc
The apt install ca-certificates curl line will prompt, for Y/n and consume the next pasted line semi-silently, culminating in this sequence not working correctly and outputting difficult-to-triage keyring errors. I believe this is the root cause of Issue #24939 and not obvious for inexperienced users. Stumbled into it myself recently but was able to recover.
Location
https://docs.docker.com/engine/install/debian/
Suggestion
add -y to install command in instructions, test on fresh installs with a minimal set of packages to find inexperienced-user issues like this.
- Dominant language
- Markdown
- Stars
- 4.7k
- Forks
- 8.5k
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 139
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from docker/docs
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
status/triage
Difficulty 1/5 Under an hour Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
[docs-scanner] Unclear policy change timing in organization policies overviewPossibly taken @Mhdomer claimed this today. Open
Difficulty 1/5 1-3 hours Newbie friendliness 89/100
Maintainers usually reply within 1 day
-
[docs-scanner] Unclear pronoun reference in cloud delivery notePossibly taken @craig-osterhout claimed this 1 day ago. Open
Difficulty 1/5 Under an hour Newbie friendliness 94/100
docker/docs#26547 · 1 assignee ·
Maintainers usually reply within 1 day
Similar issues
-
Blog update untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
sync-en
Difficulty 1/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
sync-en
Difficulty 1/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
-
Difficulty 1/5 Under an hour Newbie friendliness 83/100
GSA/digital-gov-drupal#569 ·
Maintainers usually reply within 2 days