Container manager keep terminate container on signal 9

Question

I am trying to play with Google Cloud Run, I have the same service that works fine in App Engine Flex. Any thoughts what could be the issue?

Somehow it shows that service is healthy.

Answer 1

This means infrastructure (container manager) scales down the number instances when traffic drops.

It's safe to ignore.

Answer 2

For others who find this question when their container didn't start the first time you deployed it: It's important to note that you need to have it listening on the environment variable PORT.

It appears that Cloud Run will dynamically map your container to a port at invocation, and the service that you're running needs to (dynamically) use this to serve it's content.

For reference, here's how I got the base Apache Docker image to work with Cloud Run to host a static site built via Node:

FROM node:lts AS build
COPY . .
RUN npm install
RUN npm run build

FROM httpd:latest
ENV PORT=80
RUN sed -i 's/80/${PORT}/g' /usr/local/apache2/conf/httpd.conf
COPY --from=build ./dist/ /usr/local/apache2/htdocs/