Skip to main content
General·HTTP 422·API, CLI, FE

Invalid image reference

invalid_reference

This is not a valid image reference.

What this means​

The image was empty or not written as a container image reference, or the registry credentials sent with it are incomplete.

How to fix it​

Write the image as registry/name:tag, for example nginx:1.27, and send every field the registry's credentials need.

Retry behavior​

Sending the same request again gets the same answer.

How it appears in the response​

ComputeSphere returns errors as RFC 7807 Problem Details. The type field is the docs URL for this page — switch on code in your client.

{
  "type":    "https://docs.computesphere.com/errors/invalid_reference",
  "title":   "Invalid image reference",
  "status":  422,
  "code":    "invalid_reference",
  "detail":  "This is not a valid image reference.",
  "instance": "/v2/…",
  "request_id": "f47ac10b-58cc-4372-a567-0e02b2c3d479",
  "trace_id":   null
}

The Content-Type header is application/problem+json. On field-level validation errors a non-empty errors[] array also appears, each entry carrying its own docs_url for the offending field.