please re-open, I think I know what it is

from rockcraft.

This looks like a craft-providers issue, @facundobatista and @mr-cal both recently worked on the code paths related to this, I will make sure looking into this is planned for in our upcoming sprint.

from rockcraft.

Can't manage to reproduce in 100% cases... I will reopen with a working step-by-step example when I manage to reproduce.

from rockcraft.

Update

the reported error case was caused by the introduction of base: bare in #36. This specific corner case has been fixed in d1a5f04.

I'd suggest nonetheless to keep this issue open, and ask @valentincanonical to update the description as the request is still valid for other error cases as well, like: when installing a new Rockcraft snap locally, if there is already an LXC instance from a previous build, all forthcoming builds of the same ROCK will still have the old Rockcraft version installed within the LXC instance.

Other unforeseen error cases might still occur, due to the leftover image/bundle/step dirs left within the LXC instance from previous builds.

Additionally, sensitive information might also be leftover within the LXC instance after a build.

Conclusion

I believe the issue is still valid, and we should aim to have a clean environment on every ROCK build - ideally having a new LXC instance for every build, without compromising build time

from rockcraft.