Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Destroying a clone jail does not destroy its source snapshot #42

Open
Defenso-QTH opened this issue Oct 14, 2024 · 0 comments
Open

Destroying a clone jail does not destroy its source snapshot #42

Defenso-QTH opened this issue Oct 14, 2024 · 0 comments
Assignees
@dgeo
Labels
bug Something isn't working
Milestone
future

Comments

@Defenso-QTH
Copy link
Contributor

How to reproduce

  • download release (e.g. 14.1-RELEASE)
  • create clone jail: iocage create -n testjail -r 14.1-RELEASE
  • notice there is now a 14.1-RELEASE@testjail snapshot
  • destroy the jail: iocage destroy testjail

Expected

The 14.1-RELEASE@testjail snapshot is destroyed too.

Currently

The snapshot is not destroyed. So you get an error if you try to destroy the release with iocage destroy -r 14.1-RELEASE and need to force --recursive which is dangerous.
@dgeo dgeo added the bug Something isn't working label Oct 14, 2024
@dgeo dgeo added this to the 1.9 milestone Oct 19, 2024
@dgeo dgeo self-assigned this Oct 19, 2024
@dgeo dgeo modified the milestones: 1.9, future Dec 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@dgeo dgeo

Labels
bug Something isn't working
Projects
None yet
Milestone
future
Development

No branches or pull requests
2 participants
@dgeo @Defenso-QTH