nginx / nginx/nginx.org

sudo not included in Debian dependencies

Open
#152 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
XSLT
Stars
89
Forks
60
Avg merge
19h 11m
Merged PRs (30d)
12

Description

Bug Overview

When I tried to install the Debian package provided by nginx, I encountered several failures because it was assumed that sudo was installed, which was not the case on my cloud server - it provided root access without a regular user.

In particular the sudo tee step is easy to miss the first time, and if you do not look closely the error appears to be related more to gpg, since the download completes.

Expected Behavior

I expected the installation instructions to work, accounting for the possibility that sudo was not installed, perhaps with a preface indicating that it was a dependency which must be installed separately if not already done.

Steps to Reproduce the Bug
# sudo apt install curl gnupg2 ca-certificates lsb-release ubuntu-keyring

-bash: sudo: command not found

[if sudo ignored and dependencies installed]

# curl https://nginx.org/keys/nginx_signing.key | gpg --dearmor \
    | sudo tee /usr/share/keyrings/nginx-archive-keyring.gpg >/dev/null
-bash: sudo: command not found
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 11809  100 11809    0     0  26590      0 --:--:-- --:--:-- --:--:-- 26656
gpg: [stdout]: write error: Broken pipe
gpg: [stdout]: write error: Broken pipe
gpg: filter_flush failed on close: Broken pipe
Environment Details
  • Target deployment platform: Leaseweb Virtual Machine
  • Target OS: Linux VM 6.1.0-34-cloud-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.135-1 (2025-04-25) x86_64 GNU/Linux
  • Version of this project or specific commit: Live site as of 2025-05-04
Additional Context

The VM was running a default install of Debian 12 provided by Leaseweb US, except that I had done a dist-upgrade and installed the cloud kernel instead.

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.

Research direction

Start from the Debian installation instructions containing the shown apt, curl, gpg, and sudo tee commands, and reproduce them on a root-only Debian 12 VM. Check how the instructions handle systems without sudo; done means the prerequisite or root usage is clearly documented and the key download and repository setup steps no longer fail silently in that environment.

Written by the indexing model from the issue text.

Assessment

Tech stack
debian, shell
Domain
documentation, operating-systems
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.