Skip to content

bugfix: allow DinD image to be configured via values #4018

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

Conversation

yashrajdighe
Copy link

@yashrajdighe yashrajdighe commented Apr 4, 2025

This PR allows the DinD image to be configured via Helm values by checking the container spec for a container named dind and using the defined image if present. If no custom image is specified, it defaults to docker:dind.

This change is necessary because we're hitting Docker Hub rate limits when pulling the default DinD image. By making the image configurable, we can use a custom image from our own registry, which helps avoid these limitations and improves reliability in CI workflows.

The change is already tested in the cloned chart and is working as expected.

This change makes the DinD image configurable by checking the container spec for a container named "dind" and using its defined image if present. Defaults to "docker:dind" otherwise.
@yashrajdighe yashrajdighe changed the title fix: allow DinD image to be configured via values bugfix: allow DinD image to be configured via values Apr 4, 2025
@yashrajdighe
Copy link
Author

yashrajdighe commented Apr 17, 2025

@nikola-jokic @mumoshu @toast-gear @rentziass Apologies for tagging everyone, but if possible, could someone review this PR? It's required to resolve the Docker Hub rate limiting issue we're (and many more) currently facing.

@anthony-yeong-partior
Copy link

Isnt this already configurable through the template spec in the value file? We already using custom registry and image for dind with that.

@yashrajdighe
Copy link
Author

Isnt this already configurable through the template spec in the value file? We already using custom registry and image for dind with that.

@anthony-yeong-partior Nope, its not. Its hardcoded to use docker:dind image from dockerhub which results in rate limiting.

Reference:

@nikola-jokic
Copy link
Collaborator

Closing this one since we documented that customisations to the dind mode should be applied by leaving the container mode commented out, and applying the spec we provided inside the commented section in values.yaml file.
We are aware that container mode customisations are a pain point, but there is a workaround.
Unless we support customising all fields, supporting just some fields is error-prone and hard to maintain.
See

## If any customization is required for dind or kubernetes mode, containerMode should remain

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

Successfully merging this pull request may close these issues.

3 participants