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
This makes it impossible to pull them inside air-gapped environments. Example:
Init Containers:
driver-init:
Container ID:
Image: docker.io/busybox:1.36
Operating System
Alma 8.10
CPU
AMD EPYC 9454
GPU
MI300X
ROCm Version
6.2.4
ROCm Component
No response
Steps to Reproduce
No response
(Optional for Linux users) Output of /opt/rocm/bin/rocminfo --support
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered:
Hi @boniek83 , in the code there is no registry specified in the busy box URL (the URL used is "busybox:1.36"), so its picking the default registry from your k8s environment which happens to be docker.io in Vanilla K8s. You can change the default registry of your K8s environment to be the private registry of the air-gapped environment.
What's the point of having ability to change every other image url except for init images then? I would prefer not to change cluster defaults as I'm not the only that is using this cluster and I don't know how it might impact other workloads.
Problem Description
This makes it impossible to pull them inside air-gapped environments. Example:
Init Containers:
driver-init:
Container ID:
Image: docker.io/busybox:1.36
Operating System
Alma 8.10
CPU
AMD EPYC 9454
GPU
MI300X
ROCm Version
6.2.4
ROCm Component
No response
Steps to Reproduce
No response
(Optional for Linux users) Output of /opt/rocm/bin/rocminfo --support
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered: