LinuxContainer: Allow reuse after being stopped #240
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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).