You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
currently, crio wipe checks if the node improperly shut down, and if so just removes the whole image store. this is a very heavy hammer. in containers/storage#1569@nalind added the abiliity to do consistency checks and repair the OS. We should update crio wipe to utilize them instead of removing the directory.
The text was updated successfully, but these errors were encountered:
currently, crio wipe checks if the node improperly shut down, and if so just removes the whole image store. this is a very heavy hammer. in containers/storage#1569@nalind added the abiliity to do consistency checks and repair the OS.
I need to be clear about expectations here - there isn't enough redundancy in how we store layer contents to be able to reliably repair images when we detect that some of their contents have been modified or removed: in most if not all cases, the repair logic is still going to remove what there is left of the image, with the expectation that it will be pulled again.
currently, crio wipe checks if the node improperly shut down, and if so just removes the whole image store. this is a very heavy hammer. in containers/storage#1569 @nalind added the abiliity to do consistency checks and repair the OS. We should update crio wipe to utilize them instead of removing the directory.
The text was updated successfully, but these errors were encountered: