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
looks like problem occurs because lxc cluster have second node where new container deploys.
installing pip & charmcraft on second node does not help.
I just moved container to first node:
lxc stop charmcraft-test-on-amd64-for-amd64-2359335
lxc move charmcraft-test-on-amd64-for-amd64-2359335 --target mkhn-jj-tst1
# do not start container through lxc manually! just use 'charmcraft pack'
You can also change the directory of the shared cache (defaulting the charmcraft cache directory, in this case /root/snap/charmcraft/common/cache/) by setting the CRAFT_SHARED_CACHE environment variable. More usage info is available in the Charmcraft documentation.
However, I'm not sure whether this is a sustainable operation, as you may need to create subdirectories for each Ubuntu base and each time we make incompatible changes in craft-providers. It may be better to disable caching altogether.
Would it work for you if an upcoming patch release of Charmcraft would accept setting the environment variable CRAFT_SHARED_CACHE to an empty string to disable caching?
Bug Description
Hello,
we are using lxd cluster and trying to pack a new created empty charm from scratch, but it fails with error:
pip installed
folder /root/snap/charmcraft/common/cache/charmcraft/charmcraft-buildd-base-v7/BuilddBaseAlias.JAMMY/pip exist.
To Reproduce
Environment
charmcraft.yaml
Relevant log output
The text was updated successfully, but these errors were encountered: