Cloud Run container crashing

[Gary Harrower]

Hi all,

I've recently started moving a bunch of testing services over to Cloud Run. The majority of them are running great, other than 1 API I have that goes down every couple of days.

In the logs, I see the following:

Container Sandbox: Unsupported syscall membarrier(0x8,0x0,0x0,0x2a71c55cb928,0x2a71c55cbae8,0x7). It is very likely that you can safely ignore this message and that this is not the cause of any error you might be troubleshooting. Please, refer to https://gvisor.dev/c/linux/amd64/membarrier for more information.

Uncaught signal: 11, pid=1, tid=8, fault_addr=0.

Container terminated on signal 11.

The service has the following dependencies installed:

@google-cloud/pubsub

@sentry/node

aws-sdk

axios

body-parser

bwip-js

cors

dotenv

express

firebase-admin

moment

mysql2

stripe

twilio

It seems to be pretty random. If I try and create a new revision, it sometimes restarts successfully, but other times the container fails to start back up again.

Any thoughts on what could be causing this issue?

Many thanks,

Gary

[Katayoon (Cloud Platform Support)]

Hi Gary,

Your issue seems to be similar to this reported issue on the gVisor GitHub and the troubleshooting steps and workarounds are provided in this post. You may try the recommended tips and continue with the GitHub thread if the issue still persists since you would be in direct contact with the Cloud gVisor product team to resolve the issue there.

Note that, Google Groups are reserved for general discussion on Google Cloud Platform-end products and for reporting issues or feature requests you should create a ticket in GCP Issue Tracker so that we would be able to dig into the issue/feature request more efficiently.