Why am I getting Access denied errors in Container Registry?

You have a valid IAM API key or OAuth token, but you still get Access denied errors in IBM Cloud® Container Registry.

When you try to access Container Registry, you get one of the following messages.

• You are not authorized to access the specified resource, see Why am I getting errors for a resource? for assistance.

• Insufficient scope, you might see this message if you're trying to access Container Registry by using a client such as Docker, see Why am I getting errors about insufficient scope? for assistance.

• Your account has exceeded its pull traffic quota for the current month., see Why am I getting errors about my quota? for assistance.

• Your account has exceeded its image storage quota for the current month., see Why am I getting errors about my quota? for assistance.

• You must access this account over the private network, see Why am I getting errors about using a private network? for assistance.

• Status code 403 Forbidden, you might see this message if you're using IBM Cloud Code Engine, see Why am I getting a Forbidden error when I'm using Code Engine? for assistance.

• ImagePullBackoff, you might see this status when you start containers in Kubernetes, see Why do images fail to pull from registry with ImagePullBackOff or authorization errors? for assistance.