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
{{ message }}
This repository has been archived by the owner on Nov 24, 2022. It is now read-only.
vagrant destroy will fail if your box has any associated snapshots:
Destroying drifter-jessie64-base_default_1481013000756_8417 failed: drifter-jessie64-base_default_1481013000756_8417 has snapshots.
I know Vagrant doesn't allow to create snapshots so you're not supposed to have any, but you can still create snapshots manually and in that case I'd expect vagrant destroy to still work properly. Adding the -s flag to lxc-destroy would fix this.
The text was updated successfully, but these errors were encountered:
You're right, I didn't know about this. It looks like vagrant-lxc doesn't support this though, but I guess it would be quite simple to add since it's just about forwarding the commands to lxc-snapshot.
This is something I wanted to do for a long time, but unfortunately I no longer use this plugin. I think @ccope started some work around that not long ago, not sure what's the latest info on that.
Hey, sorry for the silence here but this project is looking for maintainers 😅
As per #499, I've added the ignored label and will close this issue. Thanks for the interest in the project and LMK if you want to step up and take ownership of this project on that other issue 👋
vagrant destroy
will fail if your box has any associated snapshots:I know Vagrant doesn't allow to create snapshots so you're not supposed to have any, but you can still create snapshots manually and in that case I'd expect
vagrant destroy
to still work properly. Adding the-s
flag tolxc-destroy
would fix this.The text was updated successfully, but these errors were encountered: