This message was deleted.

It isn't recommended to do image garbage collection underneath the kubelet. I was looking at eraser prior to

imageMaximumGCAge

landing - I think that came in 1.35 though (kubernetes.io/docs/concepts/architecture/garbage-collection#…)

You're not running it right on agents. It's trying the default socket path, not the one you claim you're setting in env vars

🤦‍♂️