We've observed that the server could hang when the underlying socket returns unexpected data. The receiver thread exits immediately when an unexpected error occurs
yet the connection persists in an established state.
time="2025-12-29T15:32:51.611920734+08:00" level=error msg="error receiving message" error="read unix /run/containerd/s/ab50149a379faa1027579b7962c39bc60915ab720e02d22b78b6e13c8b20ec72->@: read: operation not permitted"