Google cloud run error "The user-provided container failed to start and listen on the port defined provided by the PORT=80 environment variable"

I have build my application using the docker file on google gcp. I am trying to run my web application build/run on tomcat.

from ubuntu <br>
COPY /mnt/opt/apache-tomcat-9.0.5/ /mnt/opt/apache-tomcat-9.0.5/ <br>
RUN apt update <br>
COPY cronjob /etc/cron.d/cronjob <br>
RUN chmod 0644 /etc/cron.d/cronjob <br>
RUN crontab /etc/cron.d/cronjob <br>
ENV CATALINA_HOME /mnt/opt/apache-tomcat-9.0.5 <br>
ENV PATH $CATALINA_HOME/bin:$PATH <br>
ENV PATH /mnt/opt/java/jdk-10.0.1/bin:$PATH <br>
ENV PORT 80 <br>
ENV HOST 0.0.0.0 <br>
EXPOSE 80 443 <br>
CMD /mnt/opt/apache-tomcat-9.0.5/bin/catalina.sh run <br>
#ENTRYPOINT ["/mnt/opt/apache-tomcat-9.0.5/bin/catalina.sh", "run"]

Using the following approach to deploy on google cloud run.

docker tag miniimagesvideos gcr.io/serious-bearing-358305/miniimagesvideos <br> docker push gcr.io/serious-bearing-358305/miniimagesvideos <br> gcloud run deploy --image=gcr.io/serious-bearing-358305/miniimagesvideos --port=80 --region=asia-southeast2 --allow-unauthenticated platform=managed --command=/mnt/opt/apache-tomcat-9.0.5/bin/catalina.sh

I keep getting error mentioned in the subject line

1. I looked at the logs and there is no additional information.
2. As per the troubleshooting steps mentioned by Google document all the requirement seems to be ok. I am able to run my application successfully on Google cloud VM. The application is build on 64 bit.
3. I have tried multiple options like using the --command, port, host parameter while trying to deploy.
4. I have tried to use CMD, instead of ENTRYPOINT in dockerfile. However, the result remains the same. I have tried to invoke tomcat using startup.sh vs Catalina.sh. But the outcome remains the same.
5. I have tried to deploy the application from GUI, but the same error comes up.

It seem container shuts down immediately while trying to deploy on Google Cloud run. Whereas, there is no issue while trying to run docker container on a Google VM.
Is there any additional configuration required for Google cloud run. Why tomcat is not able to run on Google cloud run?

This could be due to bug in gcloud. It has been fixed in the latest release. Try updating to latest version by using below command

gcloud components update

If this still doesn’t work, You could use the following flag --format=export in the command gcloud run services describe --format=export <SERVICE-NAME>
which would return the YAML file containing the configuration of the Cloud Run service. On this file you would have to change manually the fields “containerPort” and the “port” variable under “tcpSocket” in “startupProbe”.

Once you have the YAML properly configured you can use the following command to update the configuration of the service, effectively changing the port.

gcloud run services replace <yaml-file>

The following combination worked on Google Cloud run.

 1. openjdk version "11.0.18"  
 2. apache-tomcat-10.1.8

Please note i was required to implement some additional steps for my app to migrate from 9.0.75 to 10.1.8. These are trivial changes to migrate from tomcat 9.x to 10.x. <br>
SSL Connector needs an explicit tag for SSLHostconfig

    <SSLHostConfig hostName="test.test"
                       protocols="TLSv1.2">
            <Certificate certificateFile="/etc/letsencrypt/archive/miniimagesvideos.com/cert2.pem"                  certificateKeyFile="/etc/letsencrypt/archive/miniimagesvideos.com/privkey2.pem"              certificateChainFile="/etc/letsencrypt/archive/miniimagesvideos.com/chain2.pem" />
        </SSLHostConfig>
  </Connector>

In the context.xml the following needs to be added

<Loader jakartaConverter="TOMCAT" /> 

Conclusion
After multiple troubleshooting, i could reach to the following conclusion

1. Google cloud run execute Catalina.sh in a manner that the tomcat is running the background. Log indicate "Tomcat Started" and then there is another log of "container exited".

2. However, for 10.X version tomcat is kicked off as a foreground process.