Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Issue]: init containers images urls can't be changed #55

Open
boniek83 opened this issue Jan 31, 2025 · 3 comments
Open

[Issue]: init containers images urls can't be changed #55

boniek83 opened this issue Jan 31, 2025 · 3 comments
Assignees

Comments

@boniek83
Copy link

boniek83 commented Jan 31, 2025

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

@sajmera-pensando sajmera-pensando self-assigned this Feb 1, 2025
@sajmera-pensando
Copy link
Collaborator

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.

Thanks.

@boniek83
Copy link
Author

boniek83 commented Feb 1, 2025

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.

@sajmera-pensando
Copy link
Collaborator

ok, Thanks Rafal. Please let us discuss this requirement and get back to you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants