Fix run docker rename <container-id> new_name
concurrently, the container will have multi names
#33940
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.
When run
docker rename <container-id> new_name
concurrently, every operation will release oldcontainer name. So container will have multi new names reserve in nameIndex.
- What I did
Fix a bug:
Description:
docker run busybox
docker rename
command concurrentlydocker ps
anddocker inspect
, container name is different- How I did it
Every
docker rename
operation should release newest container name, so container should get locked before get container name.- How to verify it
docker rename
command concurrentlydocker ps
anddocker inspect
, container name is the sameSigned-off-by: Yang Pengfei yangpengfei4@huawei.com