[BUG] Silent hanging when collector / remover containers don't have access to CRI socket

[pmengelbert]

Version of Eraser

1.3.1

Expected Behavior

If the collector and remover containers can't connect to the CRI socket due to a file permission error, there should be an immediate error and the collector should exit with a nonzero status code.

Actual Behavior

If eraser is built with, for example, the gcr.io/distroless/static:nonroot image as a base, the collector and remover will hang indefinitely at the CRI connection stage. A connection can't be made to the mounted unix CRI socket because the nonroot user does not have file permissions for the CRI socket. The permissions are 660.

Steps To Reproduce

No response

Are you willing to submit PRs to contribute to this bug fix?

• Yes, I am willing to implement it.