google-cloud-run

Cloud Run - Requests latency

一笑奈何 提交于 2021-01-01 09:09:39
问题 I am trying to use Cloud Run to run a microservice connected to Firestore. The microservice creates objects based on s2geometry to create multiple geographical zones with specific attributes and thus help localizing users to send them information according to the zone I locate them in. I used Python 3.7 and FastAPI to create the microservice and the routes to communicate with it. The microservice runs smoothly on my local machine and on Compute Engines as most of my routes takes less than 150

Is it possible to run Postgres (or any DB) with Google Cloud Run?

别等时光非礼了梦想. 提交于 2021-01-01 05:09:39
问题 1. Summarize the problem Google Cloud Run advertises that it is "stateless containers". Is there a way to run anything at all, have it save state somewhere? I want to run Postgres in a container, but only have it up on demand, spin up the PG container when there is a request made. The same question goes for a container that will hold a REST API (web server), to connect to the PG container. So when the web app (hosted on Firebase), makes a request to the REST API (container), it would spin up,

Enter a docker container running with Google Cloud Run

不问归期 提交于 2020-12-30 06:14:07
问题 Is it possible to enter a container powered by Google Cloud Run? Something in the manner of docker exec -it CONTAINER /bin/bash ? I'm facing a bug i can't reproduce running a container based on the very same image neither locally nor using Google Cloud Shell to run that container. I'm not picky regarding whether it comes to using Cloud Shell to connect to Cloud Run or doing so from my local environment. 回答1: Is it possible to enter a container powered by Google Cloud Run? No, the only port

Enter a docker container running with Google Cloud Run

只谈情不闲聊 提交于 2020-12-30 06:12:13
问题 Is it possible to enter a container powered by Google Cloud Run? Something in the manner of docker exec -it CONTAINER /bin/bash ? I'm facing a bug i can't reproduce running a container based on the very same image neither locally nor using Google Cloud Shell to run that container. I'm not picky regarding whether it comes to using Cloud Shell to connect to Cloud Run or doing so from my local environment. 回答1: Is it possible to enter a container powered by Google Cloud Run? No, the only port

Copy files from GCS into a Cloud Run docker container during build

白昼怎懂夜的黑 提交于 2020-12-26 12:13:55
问题 I am trying to use gsutil to copy a file from GCS into a Run container during the build step. The steps I have tried: RUN pip install gsutil RUN gsutil -m cp -r gs://BUCKET_NAME $APP_HOME/artefacts The error: ServiceException: 401 Anonymous caller does not have storage.objects.get access to the Google Cloud Storage object. CommandException: 1 file/object could not be transferred. The command '/bin/sh -c gsutil -m cp -r gs://BUCKET_NAME $APP_HOME/artefacts' returned a non-zero code: 1 ERROR

Copy files from GCS into a Cloud Run docker container during build

ぐ巨炮叔叔 提交于 2020-12-26 12:13:37
问题 I am trying to use gsutil to copy a file from GCS into a Run container during the build step. The steps I have tried: RUN pip install gsutil RUN gsutil -m cp -r gs://BUCKET_NAME $APP_HOME/artefacts The error: ServiceException: 401 Anonymous caller does not have storage.objects.get access to the Google Cloud Storage object. CommandException: 1 file/object could not be transferred. The command '/bin/sh -c gsutil -m cp -r gs://BUCKET_NAME $APP_HOME/artefacts' returned a non-zero code: 1 ERROR

Error: write EPIPE on Cloud Run while using html-pdf NPM

╄→尐↘猪︶ㄣ 提交于 2020-12-15 06:50:02
问题 Here I was trying to convert HTML to PDF and used html-pdf npm (https://www.npmjs.com/package/html-pdf)). The code was running fine on local and got an issue over google cloud run. Error: write EPIPE at afterWriteDispatched (internal/stream_base_commons.js:154:25) at writeGeneric (internal/stream_base_commons.js:145:3) at Socket._writeGeneric (net.js:786:11) at Socket._write (net.js:798:8) at doWrite (_stream_writable.js:403:12) at writeOrBuffer (_stream_writable.js:387:5) at Socket.Writable

Is it posible to expose 5001 (HTTP) and 5672 (TCP) ports in a Cloud Run Service?

谁都会走 提交于 2020-12-15 02:58:40
问题 I am setting up a solution in Google Cloud. I need a RabbitMQ queue broker and a WebAPI developed in .NET Core 2.2. The idea is for the WebAPI to connect to RabbitMQ to receive messages. I have mounted RabbitMQ with GKE in a cluster of kubernetes with RabbitMQ Cluster, obtained in Marketplace. I have mounted the WebAPI in Cloud Run. Both components are raised in a standard way, without any particularity for publication. The WebAPI uses port 5001 for HTTP traffic, and apparently the listener

Is it posible to expose 5001 (HTTP) and 5672 (TCP) ports in a Cloud Run Service?

谁都会走 提交于 2020-12-15 02:57:35
问题 I am setting up a solution in Google Cloud. I need a RabbitMQ queue broker and a WebAPI developed in .NET Core 2.2. The idea is for the WebAPI to connect to RabbitMQ to receive messages. I have mounted RabbitMQ with GKE in a cluster of kubernetes with RabbitMQ Cluster, obtained in Marketplace. I have mounted the WebAPI in Cloud Run. Both components are raised in a standard way, without any particularity for publication. The WebAPI uses port 5001 for HTTP traffic, and apparently the listener

Is it posible to expose 5001 (HTTP) and 5672 (TCP) ports in a Cloud Run Service?

六眼飞鱼酱① 提交于 2020-12-15 02:56:03
问题 I am setting up a solution in Google Cloud. I need a RabbitMQ queue broker and a WebAPI developed in .NET Core 2.2. The idea is for the WebAPI to connect to RabbitMQ to receive messages. I have mounted RabbitMQ with GKE in a cluster of kubernetes with RabbitMQ Cluster, obtained in Marketplace. I have mounted the WebAPI in Cloud Run. Both components are raised in a standard way, without any particularity for publication. The WebAPI uses port 5001 for HTTP traffic, and apparently the listener