Closed mthaddon closed 3 years ago
Because that charm is using layer:caas-base
, this error is actually coming from that layer's custom WheelhouseTactic
implementation. Interestingly, the approach that that layer's tactic uses is more similar to the way charmcraft
pre-builds the venv rather than building it at deploy time the way the default WheelhouseTactic
does, but it has also gotten out of sync with the default tactic and missed some fixes and improvements made to that tactic.
The charmcraft
/ layer:caas-base
approach has significant performance advantages during install and upgrade, but has the downside of opening the charm up to architecture-specific binaries ending up in the charm. This will be addressed with Metadata v2 and CharmHub via the extended architecture info, but it might be worth considering adding that type of build as an option in the current default tactic and fold layer:caas-base
's custom tactic back into the default.
Upon further review, this actually came in from https://github.com/juju/charm-tools/pull/585 (specifically, this section).
This could (and probably should) still be fixed in the caas-base layer (by at least porting over the improvements to combine the wheelhouse.txt
file from each layer and doing the install at the end rather than per-layer, which came in #569), but in the meantime, you can work around it by adding the --ignore-lock-file
option to your charm build
call when building k8s charms.
Ok, closing this in favor of https://github.com/juju-solutions/layer-caas-base/issues/27 and https://github.com/juju/charm-tools/issues/596
What version am I running?
I ran the following command:
snap info charm
and got the following ouput:I am using: ubuntu 20.04
Running the following:
I get this error: