-
Notifications
You must be signed in to change notification settings - Fork 3k
Open
Labels
Good First IssueThis issue would be a good issue for a first time contributor to undertake.This issue would be a good issue for a first time contributor to undertake.documentationIssue or fix is in project documentationIssue or fix is in project documentationkind/bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.triagedIssue has been triagedIssue has been triagedvolunteers-wantedIssues good for community/volunteer contributionsIssues good for community/volunteer contributions
Description
Issue Description
Look at the podman push -h output:
Push an image to a specified destination
[...]
Usage:
podman push [options] IMAGE [DESTINATION]
Examples:
podman push imageID docker://registry.example.com/repository:tag
podman push imageID oci-archive:/path/to/layout:image:tag
Options:
Note how the second example is way off to the right. Source code:
podman/cmd/podman/images/push.go
Lines 44 to 45 in 509e44a
| Example: `podman push imageID docker://registry.example.com/repository:tag | |
| podman push imageID oci-archive:/path/to/layout:image:tag`, |
// Command: podman push
pushCmd = &cobra.Command{
Use: "push [options] IMAGE [DESTINATION]",
// [...]
Example: `podman push imageID docker://registry.example.com/repository:tag
podman push imageID oci-archive:/path/to/layout:image:tag`,
}I suppose, the backticks string were meant to strip leading whitespaces, but they never actually behaved that way in Go?
This issue is present in many other commands, not just push!
Steps to reproduce the issue
Steps to reproduce the issue
podman push -h
Describe the results you received
Second example is indented.
Describe the results you expected
Second example should not be indented.
podman info output
version:
APIVersion: 5.5.2
Built: 1754604929
BuiltTime: Fri Aug 8 01:15:29 2025
GitCommit: e7d8226745ba07a64b7176a7f128e4ef53225a0e
GoVersion: go1.24.5
Os: linux
OsArch: linux/amd64
Version: 5.5.2Podman in a container
No
Privileged Or Rootless
Rootless
Upstream Latest Release
No
Additional environment details
No response
Additional information
No response
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
Good First IssueThis issue would be a good issue for a first time contributor to undertake.This issue would be a good issue for a first time contributor to undertake.documentationIssue or fix is in project documentationIssue or fix is in project documentationkind/bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.triagedIssue has been triagedIssue has been triagedvolunteers-wantedIssues good for community/volunteer contributionsIssues good for community/volunteer contributions