You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The user would like to authenticate with a container registry after buildah login. Buildah generates an authentication file in ${XDG_RUNTIME_DIR}/containers/auth.json. ORAS doesn't support reading credential store from Buildah authentication file.
Buildah config file is similar to docker but it supports repo/namespace level auth.
Expected behavior:
If the user has Buildah installed on the system and used buildah login to authenticate with an OCI-compliant registry, the user's credentials are already stored and available to ORAS. In this case, the user doesn't need to run oras login again to authenticate with an OCI-compliant registry.
The user would like to authenticate with a container registry after buildah login. Buildah generates an authentication file in ${XDG_RUNTIME_DIR}/containers/auth.json. ORAS doesn't support reading credential store from Buildah authentication file.
Buildah config file is similar to docker but it supports
repo/namespace
level auth.Expected behavior:
If the user has Buildah installed on the system and used buildah login to authenticate with an OCI-compliant registry, the user's credentials are already stored and available to ORAS. In this case, the user doesn't need to run
oras login
again to authenticate with an OCI-compliant registry.Related issue: notaryproject/notation#1058
The text was updated successfully, but these errors were encountered: