You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The following workflow is required to more easily integrate [cluster-api-k8s](https://github.com/canonical/cluster-api-k8s) into the https://sylva-projects.gitlab.io/ project:
Create an Ubuntu Image using disk-image-builder project as per Sylva requirements - to contain the k8s binaries
Use that Ubuntu Image with cluster-api-k8s
An issue arises with this workflow, as the disk-image-builder relies on a chroot environment, thus there is no way to pre-install a snap, in this case k8s snap.
A workaround would be to just download the snap files for the k8s snap: snap download k8s, and it is possible to do it at a known path in the image, let's say /capi/snap-binaries and an image to be created.
Afterwards, using the localPath = /capi/snap-binaries/k8s.snap in the CK8sConfig, the installation of the snap k8s cannot be done in an airgapped environment (airgapped environment = no access to the Internet), because the snap k8s is not an independent snap, as it depends on the core20 snap.
Because of this, there is no way to actually use the LocalPath feature of the cluster-api-k8s in an airgapped environment, as it will always fail because snapd cannot download the core20 snap.
Is this behaviour intentional? It would be great to have a way to either be able to install a snap in a chrooted environment. Or to carry over the dependent snaps with you and snap to automatically try to install those snaps from the same directory. Or to have cluster-api-k8s install the core20 snap from the root dir of the LocalPath.
Thank you.
The text was updated successfully, but these errors were encountered:
Hello,
The following workflow is required to more easily integrate
[cluster-api-k8s](https://github.com/canonical/cluster-api-k8s)
into thehttps://sylva-projects.gitlab.io/
project:cluster-api-k8s
An issue arises with this workflow, as the disk-image-builder relies on a chroot environment, thus there is no way to pre-install a snap, in this case
k8s
snap.A workaround would be to just download the snap files for the k8s snap:
snap download k8s
, and it is possible to do it at a known path in the image, let's say/capi/snap-binaries
and an image to be created.Afterwards, using the
localPath = /capi/snap-binaries/k8s.snap
in the CK8sConfig, the installation of the snapk8s
cannot be done in an airgapped environment (airgapped environment = no access to the Internet), because the snapk8s
is not an independent snap, as it depends on thecore20
snap.Because of this, there is no way to actually use the
LocalPath
feature of thecluster-api-k8s
in an airgapped environment, as it will always fail because snapd cannot download thecore20
snap.Is this behaviour intentional? It would be great to have a way to either be able to install a snap in a chrooted environment. Or to carry over the dependent snaps with you and snap to automatically try to install those snaps from the same directory. Or to have
cluster-api-k8s
install thecore20
snap from the root dir of theLocalPath
.Thank you.
The text was updated successfully, but these errors were encountered: