nextcloud / nextcloud/helm

Failed to inspect image

Open Beginner friendly
#856 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go Template
Stars
534
Forks
314
Avg merge
42m
Merged PRs (30d)
1

Description

Hello everyone,
I've deployed v9.1 of the helm chart. Because global.image.registry is empty, the registry is not set for the container image, even if the registry was defined under image.registry, for example. I think the issue here is due to the coalesce in the template function.

https://github.com/nextcloud/helm/blob/682ce2ffd2d3126da2df5b9a62605a1dc9910043/charts/nextcloud/templates/_helpers.tpl#L46

Kubernetes environments that rely on cri-o have been encountering an error since version 1.34 because no default registry such as docker.io is defined. This change was introduced in version 1.34 of kubernetes/crio. With this change and the usage of unqualified images environments throw the following issue:

spec.containers{nextcloud}: Failed to inspect image "": rpc error: code = Unknown desc = short-name "library/nextcloud:32.0.1-apache" did not resolve to an alias and no unqualified-search registries are defined in "/etc/containers/registries.conf"

Please fix the error by adjusting the template function or assigning a value to global.image.registry.

To prevent this error in the future, Helm unit tests would be a suitable solution.

Best regards,
Volker

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start in charts/nextcloud/templates/_helpers.tpl around line 46 and inspect how the coalesce function handles global.image.registry versus image.registry. Reproduce the empty-registry rendering case, then add Helm unit coverage for the registry values and verify that the rendered container image is no longer unqualified.

Written by the indexing model from the issue text.

Assessment

Tech stack
helm, kubernetes
Domain
devops, infrastructure
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
68/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.