Skip to content
This repository has been archived by the owner on Nov 24, 2022. It is now read-only.

Add -s flag to lxc-destroy #429

Closed
sephii opened this issue Dec 6, 2016 · 4 comments
Closed

Add -s flag to lxc-destroy #429

sephii opened this issue Dec 6, 2016 · 4 comments
Labels

Comments

@sephii
Copy link

sephii commented Dec 6, 2016

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.

@strarsis
Copy link

strarsis commented Dec 6, 2016

Doesn't vagrant offer snapshots, at least for native providers like virtualbox? https://www.vagrantup.com/docs/cli/snapshot.html

@sephii
Copy link
Author

sephii commented Dec 6, 2016

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.

@fgrehm
Copy link
Owner

fgrehm commented Dec 6, 2016

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.

@fgrehm fgrehm added the ignored label Nov 17, 2022
@fgrehm
Copy link
Owner

fgrehm commented Nov 17, 2022

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 👋

@fgrehm fgrehm closed this as completed Nov 17, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants