Skip to content
This repository has been archived by the owner on Jan 22, 2024. It is now read-only.

Container image can not be found #6

Closed
volker-raschek opened this issue Jan 25, 2021 · 0 comments · Fixed by #9
Closed

Container image can not be found #6

volker-raschek opened this issue Jan 25, 2021 · 0 comments · Fixed by #9

Comments

@volker-raschek
Copy link

Hello,
I have use on all of my cluster nodes crio as container runtime. Per default on Arch Linux no registries are configured. This leads to the error, that the image busybox can not be found. I forked not the git repository to change the relative to the absolute path of the image.

Please, can you make the path configurable for the busybox image?
@bsctl bsctl mentioned this issue Feb 13, 2021
Merged
@bsctl bsctl closed this as completed in #9 Feb 13, 2021
bsctl referenced this issue Feb 13, 2021
@bsctl
Merge pull request #9 from clastix/issues/6
849e820 
make installer image configurable
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

make installer image configurable bsctl/kubelived
1 participant
@volker-raschek