Closed floriankoch closed 2 years ago
I'm not able to reproduce this issue.
These are the steps I took:
role
(line 20) to be acrpush
~/.docker/config.json
to ensure I didn't have an entry for this freshly created registrydocker login -u <value provided by the script> <fqdn registry>
- once prompted for the password, I entered the one returned by the scriptdocker push
kwctl pull ghcr.io/kubewarden/policies/allow-privilege-escalation-psp:v0.1.11
kwctl push registry://ghcr.io/kubewarden/policies/allow-privilege-escalation-psp:v0.1.11 <registry>.azurecr.io/kubewarden/policies/allow-privilege-escalation-psp:v0.1.11
crane
tool: crane manifest <registry>.azurecr.io/kubewarden/policies/allow-privilege-escalation-psp:v0.1.11
The push took place from my personal computer running Linux on x64_64
@floriankoch which version of kwctl are you using?
@kubewarden/kubewarden-developers : moving to "external block" on our project board, waiting for more feedback
Closing, feel free to reopen with you are still experiencing this issue. As I said, I cannot reproduce that.
Is there an existing issue for this?
Current Behavior
This is similar to https://github.com/kubewarden/kwctl/issues/208
Push does not works after Docker Login Push with wasm-to-oci works
Expected Behavior
Push works
Steps To Reproduce
No response
Environment
Anything else?
No response