Skip to content

[Documentation]: Always use FQDM for container images #446

Description

@leo8a

Description of errors

Documentation Issue: Device Config Manager Image Missing FQDN

Documentation Page

https://instinct.docs.amd.com/projects/gpu-operator/en/latest/dcm/applying-partition-profiles.html

Problem

The documentation uses a non-FQDN image reference that fails in OpenShift and other environments with short name enforcement:

image: "rocm/device-config-manager:v1.4.0"

Error

Warning  InspectFailed: Failed to inspect image "": rpc error: code = Unknown desc = short name mode is enforcing, but image name rocm/device-config-manager:v1.4.0 returns ambiguous list

Solution

Use the fully qualified domain name:

image: "docker.io/rocm/device-config-manager:v1.4.0"

Impact

  • Blocks users on OpenShift/Podman environments with short name enforcement
  • Affects the kubectl patch deviceconfig command in the "Enabling Device Config Manager" section

Environment

  • OpenShift 4.x
  • Podman/CRI-O with short name enforcement enabled

Attach any links, screenshots, or additional evidence you think will be helpful.

No response

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions