Using the OADP stable 1.1 channel on Openshift, when running a velero restore for a deployment with an attached pvc, the restic init container prevents the velero restore from completing with an Init:CreateContainerConfigError message. Full error from pod description:

{{ Warning Failed 96m (x12 over 98m) kubelet Error: container has runAsNonRoot and image has non-numeric user (nobody), cannot verify user is non-root (pod: "<pod name>)", container: restic-wait)}}

{{}}

This error hangs the velero restore and never self corrects. The environment where I copied the error message from first saw the problem a week ago and the pod is still in the same state.{}

{{}}

I found a related issue in the vmware-tanzu repo that ostensibly resolved this problem but I have been experiencing this problem frequently as of late.

Restarting the pod does not resolve the issue and so far the only workaround I have found is to delete the deployment altogether and redeploy it without the restic init container (it's my understanding this container is only meant to wait for the necessary resources to be restored by velero anyway)