Skip to content

rmi: reject docker transport image references - #29332

Open
Rajkaran-122 wants to merge 1 commit into
podman-container-tools:mainfrom
Rajkaran-122:fix-rmi-docker-transport-error
Open

rmi: reject docker transport image references#29332
Rajkaran-122 wants to merge 1 commit into
podman-container-tools:mainfrom
Rajkaran-122:fix-rmi-docker-transport-error

Conversation

@Rajkaran-122

@Rajkaran-122 Rajkaran-122 commented Jul 29, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Update podman rmi to reject docker:// image references before image removal is attempted.
  • This avoids the generic "unsupported transport" error and returns a clearer error indicating that transport-qualified
  • image references are not supported for local image removal.
  • An e2e test has been added to cover this behavior.

Referenced issue:
Non-actionable error message: 'Error: unsupported transport "docker" for looking up local images' #20775

Checklist

Ensure you have completed the following checklist for your pull request to be reviewed:

  • Certify you wrote the patch or otherwise have the right to pass it on as an open-source patch by signing all
    commits. (git commit -s). (If needed, use git commit -s --amend). The author email must match
    the sign-off email address. See CONTRIBUTING.md
    for more information.
  • Referenced issues using Fixes: #00000 in commit message (if applicable)
  • Tests have been added/updated (or no tests are needed)
  • Documentation has been updated (or no documentation changes are needed)
  • All commits pass make validatepr (format/lint checks)
  • Release note entered in the section below (or None if no user-facing changes)

Does this PR introduce a user-facing change?

Does this PR introduce a user-facing change?

When `podman rmi` is invoked with `docker://{image}`, a clearer error is now returned instead of the generic unsupported transport error.

Signed-off-by: Rajkaran Yadav <yadavrajkaran854@gmail.com>

@Luap99 Luap99 left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

#29334 (review)

in general similar chnage would be nice to consolidate into one PR so we can have that discussion once, using muliple commit per command itself is fine

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants