bugfix: umount rootfs when delete a container #2196
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.
Signed-off-by: Michael Wan zirenwan@gmail.com
Ⅰ. Describe what this PR did
When using PouchContainer to replace the old container engine in Alibaba Group, we must take over the old running containers. Maybe somebody has known that we use d2p-migrator to convert those old containers to pouch containers
Since those old containers are not created by
pouchd
, but taking over by specified a rootfs for container, the remove action is different from normal containers. We no need to delete the snapshot of container because old containers have no snapshots, then we also shouldumount
the rootfs when delete the container.Ⅱ. Does this pull request fix one issue?
None
Ⅲ. Why don't you add test cases (unit test/integration test)? (你真的觉得不需要加测试吗?)
It is difficult to imitate the situation of taking over containers, So i will add test case in
d2p
test.Ⅳ. Describe how to verify it
None
Ⅴ. Special notes for reviews
None