This message was deleted.
# harvestera
adamant-kite-43734
02/15/2023, 2:40 PMThis message was deleted.
👍 1
g
great-bear-19718
02/15/2023, 10:53 PMthis image is an image created at runtime and only contains internal artefacts and is packaged within the iso
great-bear-19718
02/15/2023, 10:53 PMduring the install process, we copy images and extract them for rke2
great-bear-19718
02/15/2023, 10:55 PMi have seen in some scenarios when using iso, the extract can fail silently, likely because image extraction took over 30 mins, in which case you can see node boot and complain about the missing image
great-bear-19718
02/15/2023, 10:55 PMbest option would be to retry iso install or try a PXE based install, which downloads iso locally onto node, and runs into less issues during the image extract
great-bear-19718
02/15/2023, 10:55 PMi hope this helps
f
flat-finland-50817
02/16/2023, 8:32 AMThanks for the explanations, we will retry the install. May I ask why this image is not available publicly in a registry ? What is the benefit of only packaging it in the iso and not give access to it by registry ?
flat-finland-50817
02/20/2023, 8:03 AMWe were able to finish the install by extracting the
harvester-cluster-repog
great-bear-19718
02/20/2023, 9:27 AMits only use is to hold individual helm charts for some of the core components already published as separate releases
f
flat-finland-50817
02/20/2023, 9:34 AMBut why not uploading it to a public registry (like docker.io or registry.suse.com) ? As it could prevent installation failures ? Is it vendor proprietary or something like that ?
g
great-bear-19718
02/20/2023, 9:37 AMone it will not work in air-gapped env, and issue is to figure out why extraction is failing silently
k
kind-librarian-59515
02/20/2023, 10:02 AMissue is to figure out why extraction is failing silentlyYou are correct 🙂: we can create an issue out of this Slack conversation if you want.
one it will not work in air-gapped envThe question is not wether you should embed or not the container images in the harvester ISO: of course you should embed all the needed container images in the Harvester ISO file. The question is to allow people to audit and review the container images that are embedded in the ISO. This is exactly what is done on the k3s github: there are files called "k3s-airgap-images-amd64.tar*", which anyone can review and audit and then use in their own k3s airgap installation 😊. The image "*harvester-cluster-repo*" is nowhere to be found, exept in the harvester ISO. We do not know where and how the ISO is fabricated. We do not know where and how the container image is fabricated. Does this mean it is a rancher vendor/proprietary container image, and not an open source container image? Are there other container images that follows the same behaviour (for RKE2)? What is the licensing behind Harvester?
g
great-bear-19718
02/20/2023, 10:03 AMgreat-bear-19718
02/20/2023, 10:04 AMgreat-bear-19718
02/20/2023, 10:04 AMif you have docker on x86 just run
make build-isok
kind-librarian-59515
02/20/2023, 10:09 AM[edit link] Thank you, this helps 🙂. Can you confirm that this image
rancher/harvester-cluster-repo:v1.1.1kind-librarian-59515
02/20/2023, 10:34 AMThanks to your help, I also discover the rancher tool "wharfie", which seems to have the same sort of features than "`crane export`" or "`podman/docker save`" or "`skopeo copy`".
https://github.com/rancher/wharfie
29 Views