-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
remote: manifest add --annotation failed to add annotations field #15952
Comments
I think this was fixed for |
|
Ah fair enough then I think this is not wired on the remote at all. |
I see, it means --annotation option isn't supported on remote environment. |
@sstosh Yes I think entire annotate command is not yet implemented https://github.com/containers/podman/blob/main/pkg/domain/infra/tunnel/manifest.go#L81 |
This should be supported, lets fix the bug. |
Sure, I'll try to fix this bug. |
* `manifest add --annotation option` adds annotations field on remote environment. * `manifest inspect` prints annotations field on remote environment. Fixes: containers#15952 Signed-off-by: Toshiki Sonoda <[email protected]>
* `manifest add --annotation option` adds annotations field on remote environment. * `manifest inspect` prints annotations field on remote environment. Fixes: #15952 Signed-off-by: Toshiki Sonoda <[email protected]>
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
In help page, podman-remote manifest add --annotation option seems to be supported.
However, --annotation option doesn't work.
Steps to reproduce the issue:
Describe the results you received:
Describe the results you expected:
Additional information you deem important (e.g. issue happens only occasionally):
Succeeded to add annotations field on local enviornment.
podman-remote version
podman-remote info
Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide? (https://github.com/containers/podman/blob/main/troubleshooting.md)
Yes
Additional environment details (AWS, VirtualBox, physical, etc.):
KVM, fedora36
The text was updated successfully, but these errors were encountered: