Wipe local container storage clean
To ensure that container images with sigstore signatures are correctly downloaded and verified, you must clear existing local storage. Removing previous container data prevents configuration conflicts when you update security policies for MicroShift.
-
You have administrator access to the MicroShift host.
-
You enabled sigstore on your mirror registries.
-
Stop the CRI-O container runtime service and MicroShift by running the following command:
$ sudo systemctl stop crio microshift -
Wipe the CRI-O container runtime storage clean by running the following command:
$ sudo crio wipe --force -
Restart the CRI-O container runtime service and MicroShift by running the following command:
$ sudo systemctl start crio microshift
Verify that all pods are running in a healthy state by entering the following command:
$ oc get pods -A
NAMESPACE NAME READY STATUS RESTARTS AGE
default i-06166fbb376f14a8bus-west-2computeinternal-debug-qtwcr 1/1 Running 0 46m
kube-system csi-snapshot-controller-5c6586d546-lprv4 1/1 Running 0 51m
openshift-dns dns-default-45jl7 2/2 Running 0 50m
openshift-dns node-resolver-7wmzf 1/1 Running 0 51m
openshift-ingress router-default-78b86fbf9d-qvj9s 1/1 Running 0 51m
openshift-ovn-kubernetes ovnkube-master-5rfhh 4/4 Running 0 51m
openshift-ovn-kubernetes ovnkube-node-gcnt6 1/1 Running 0 51m
openshift-service-ca service-ca-bf5b7c9f8-pn6rk 1/1 Running 0 51m
openshift-storage topolvm-controller-549f7fbdd5-7vrmv 5/5 Running 0 51m
openshift-storage topolvm-node-rht2m 3/3 Running 0 50m
|
|
This example output shows a basic MicroShift installation. If you installed optional RPMs, the status of pods running those services is displayed in the output. |