Replies: 2 comments
-
@haircommander please see |
Beta Was this translation helpful? Give feedback.
0 replies
-
would you mind opening an issue with the use cases describing why you need containers to stay after a reboot? the container process will not be the same, and the kubelet should be the one keeping track of the containers that should be created. if cri-o keeps track of them (or, really, recreates them after the reboot), then the kubelet can get confused and double create things, which is tricky to detect and resolve quickly |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I see that earlier there was an option "internal_wipe". It is documented at https://github.com/cri-o/cri-o/blob/main/docs/crio.conf.5.md
This option, if set false", would prevent containers to be wiped after reboot.
But this is marked as DEPRECATED.
What can be used now?
Beta Was this translation helpful? Give feedback.
All reactions