Skip to content

LinuxContainer: Allow reuse after being stopped #240

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.

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

Merged
merged 1 commit into from
Aug 6, 2025

Conversation

dcantah
Copy link
Member

@dcantah dcantah commented Jul 30, 2025

After the container is stopped it's a bit odd how we don't allow the object to be restarted. If someone wanted to continuously rerun the same container they'd need to make a new object every time even though all guest state is blown away on stop() so it's a clean slate.

This change makes it so that you can create+start again after stop (although create stands out like a sore thumb now as stop -> create is just strange).

After the container is stopped it's a bit odd how we don't allow
the object to be restarted. If someone wanted to continuously
rerun the same container they'd need to make a new object every time
even though all guest state is blown away on stop() so it's a clean
slate.

This change makes it so that you can create+start again after stop
(although create stands out like a sore thumb now as stop -> create
is just strange).
@dcantah dcantah merged commit 4d2f73d into apple:main Aug 6, 2025
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants