cli/registry/login: Add the `--password-env` flag
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 6.1k
- Forks
- 2.2k
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 43
Description
Description
Add support for providing registry passwords via environment variables, which is particularly useful in CI pipelines. For example, GitLab stores registry passwords in the CI_REGISTRY_PASSWORD environment variable.
With the --password-env flag, authenticating to a registry is as simple as:
docker login --username "${CI_REGISTRY_USER}" --password-env "CI_REGISTRY_PASSWORD" "${CI_REGISTRY}"
Alternatives Considered
-
Using
docker login -p "${VAR}"with warning suppression- Shell history concerns don't apply with variable substitution
- Tokens are often short-lived, reducing security concerns
- Could introduce a way to suppress warnings via environment variables
-
Passing passwords via STDIN (current recommended method):
echo "${CI_REGISTRY_PASSWORD}" | docker login --username "${CI_REGISTRY_USER}" --password-stdin "${CI_REGISTRY}"Avoids warnings but adds complexity to command chains
Contributor 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.
Research direction
Start by locating the Docker CLI's login command and its existing --password-stdin handling. Trace how command-line flags reach authentication, then verify that --password-env reads the named environment variable and supports the GitLab CI example without exposing the password.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100