-
Notifications
You must be signed in to change notification settings - Fork 350
Use containerd image readiness check function to properly recover image during restart. #303
Comments
I can help on this. @Random-Liu |
Not decided yet. I think at least not next week. :) |
I will enjoy my holiday:) |
containerd/containerd#1567 is merged. |
@yanxuean Please only check image readiness during restart recovery for now. We'll consider whether we should always check readiness in list and inspect later. And when check readiness, you need to use the new containerd function to check whether all contents are present, and also whether the top level snapshot exists (with ChainID). If yes, good to add the image into our image store. |
fix containerd#303 Signed-off-by: yanxuean <yan.xuean@zte.com.cn>
@Random-Liu I hit some problem. I need your help. Seem like The Stat() only check if it is exist in io.containerd.metadata.v1.bolt/meta.db.
|
fix containerd#303 Signed-off-by: yanxuean <yan.xuean@zte.com.cn>
@Random-Liu need help :) |
fix containerd#303 Signed-off-by: yanxuean <yan.xuean@zte.com.cn>
fix containerd#303 Signed-off-by: yanxuean <yan.xuean@zte.com.cn>
fix containerd#303 Signed-off-by: yanxuean <yan.xuean@zte.com.cn>
fix containerd#303 Signed-off-by: yanxuean <yan.xuean@zte.com.cn>
fix containerd#303 Signed-off-by: yanxuean <yan.xuean@zte.com.cn>
Currently, during restart we read all image references from containerd image metadata store, and recover the image list.
However, a image reference in containerd image metadata store doesn't mean the image is ready for use, the image could be corrupted because of aborted image pulling.
We should use the newly added
Check
function containerd/containerd#1567 to check content completeness and check top level snapshot existence.The text was updated successfully, but these errors were encountered: