[Documentation]: Always use FQDM for container images
Open
@nikhilsk is already working on this.
Since Mar 25, 2026.
- Dominant language
- Go
- Stars
- 105
- Forks
- 57
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 12
Description
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 deviceconfigcommand 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
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.