cri-o cri checkpoint feature #6749
-
hello everyone , in readed this blog post about the new alpha kubelet checkpoint api feature and i wanted to test it but i found that the new image generated from the checkpoint is smaller then first image and when i tied to pull it again i got an error "NO command specified" , mor details are in this issue kubernetes/kubernetes#116744 (comment) . |
Beta Was this translation helpful? Give feedback.
Replies: 6 comments 48 replies
-
@adrianreber WDYT |
Beta Was this translation helpful? Give feedback.
-
@abdelghanimeliani please try with the latest version of CRI-O from git. I think this is related to a fix latest CRI-O git has. A workaround could be to start CRI-O with Or start the container with |
Beta Was this translation helpful? Give feedback.
-
@adrianreber , for some reason , im not able to build the package from the source code , is this fix included in version 1.26.1 or 1.26.2 ? |
Beta Was this translation helpful? Give feedback.
-
@adrianreber im using the last version of crio from git and go1.19 , i tried to run the pod with shareProcessNamespace: true and to to start CRI-O with --drop-infra-ctr=false , the same problem reported in kubernetes repo is happening |
Beta Was this translation helpful? Give feedback.
-
@adrianreber |
Beta Was this translation helpful? Give feedback.
-
One thing we did to make this work was disable copy on write on btrfs with |
Beta Was this translation helpful? Give feedback.
One thing we did to make this work was disable copy on write on btrfs with
chattr +C
. Also see https://criu.org/Filesystems_pecularities