Closed przemeklal closed 1 year ago
Workaround: snap download core22, scp it to the target units and install manually there.
@przemeklal I assume that this air-gapped environment is not using snap store proxy either, right? So the only way is to manually attach snap as a resource?
In this particular environment attaching core22 as a resource would be the only possible option. It would be the same solution that is used in the p-o-e charm for example.
I think that for now we won't be resolving this issue as the recommended way of dealing with air-gapped environments is to use Snap Store Proxy and it's also the direction that some other big charms are taking (e.g. kubernetes-control-plane)
I tried to deploy the charm in a "temporarily air-gapped" environment but it failed with the following error:
I attached the local snap as follows:
But snap
core22
was still missing and currently, it's impossible to attach it as the resource.My proposal is to implement a new resource for the
core
snap, similar to how other charms do it.