Google Cloud Run gVisor syscall error on node application

Question

My project was running successfully on cloud run and I recently added https://www.npmjs.com/package/express-static-gzip package to serve my pre gzipped assets and what I noticed is after deploying to cloud run the pre gzipped assets are not recognized by the browser (it's working perfectly on localhost)

Also I noticed an error in stackdriver logs.

Container Sandbox Limitation: Unsupported syscall statx(0xffffff9c,0x3e2292ff7208,0x0,0xfff,0x3e2292ff6df0,0x3e2292ff6f10). Please, refer to https://gvisor.dev/c/linux/amd64/statx for more information.

Also noticed the assets served from google cloud run don't have accept-encoding header (When looking into the source code of express-static-gzip package, it uses nodejs file read calls, I assume that file read calls may causing error in gVisor)

Update:

Getting this "Container Sandbox Limitation: Unsupported syscall" error even after removing express-static-gzip package too.

Does anyone know about this error?

Answer 1

AFAIK the "statx" system call is implemented in gVisor (since June 19). Maybe Cloud Run isn't using the latest release yet.

Answer 2

This is worth noting while running on Google Cloud Run when you see unsupported syscall error in logs:

Most of the time, failed syscalls don’t mean your app is failing. Node.js, here, is trying to use statx if it’s available, and falling back to stat system call, which is supported.

Most languages will explicitly print a stack trace while crashing or they will throw an exception when the system call fails. I don’t see that happening here.