Open sumitaneja opened 3 years ago
Wasme falls back to using the docker credentials when it's talking to a non-wasmhub registry. If you use docker login
to log into the registry first, then wasme push
will use those credentials.
@Sodman this is not working
docker login iad.ocir.io/<repo>
Authenticating with existing credentials...
Login Succeeded
wasme push iad.ocir.io/<repo>/<image>:v1
INFO[0000] Pushing image iad.ocir.io/<repo>/<image>:v1
Error: All attempts fail:
#1: oras push failed: no scope specified for token auth challenge
wasme --version wasme version 0.0.33
Looks like this would be solved by implementing https://github.com/solo-io/wasm/issues/241 - for now it looks like that user managed a workaround, see this comment for more details.
@Sodman no luck
oras login iad.ocir.io/<repo>
Username: <uname>
Password: <pwd>
Login Succeeded
wasme push iad.ocir.io/<repo>/<image>:v1
INFO[0000] Pushing image iad.ocir.io/<repo>/<image>:v1
Error: All attempts fail:
#1: oras push failed: no scope specified for token auth challenge
Using Oracle cloud infra repository which is compliant with OCI registry https://docs.oracle.com/en-us/iaas/Content/Registry/Concepts/registryoverview.htm
cli fails in login with not found.
for wasme push gves below error oras push failed: no scope specified for token auth challenge