google-cloud-run

Expose Both Ports 8080 and 3000 For Cloud Run Deployment

血红的双手。 提交于 2020-07-09 05:27:08
问题 TL:DR - I am trying to deploy my MERN stack application to GCP's Cloud Run. Struggling with what I believe is a port issue. My React application is in a client folder inside of my Node.js application. Here is my one Dockerfile to run both the front-end and back-end: FROM node:13.12.0-alpine WORKDIR /app COPY . ./ # Installing components for be connector RUN npm install --silent WORKDIR /app/client RUN npm install --silent WORKDIR /app RUN chmod +x /app/entrypoint.sh ENTRYPOINT [ "/app

How can I specify a region for the Cloud Storage buckets used by Cloud Build for a Cloud Run deployment?

 ̄綄美尐妖づ 提交于 2020-07-08 05:49:48
问题 When deploying a docker container image to Cloud Run, I can choose a region, which is fine. Cloud Run delegates the build to Cloud Build, which apparently creates two buckets to make this happen. The unexpected behavior is that buckets aren't created in the region of the Cloud Run deployment, and instead default to multi-region US. How do I specify the region as "us-east1" so the cost of storage is absorbed by the "always free" tier? (Apparently US multi-region storage buckets store data in

How can I specify a region for the Cloud Storage buckets used by Cloud Build for a Cloud Run deployment?

点点圈 提交于 2020-07-08 05:48:47
问题 When deploying a docker container image to Cloud Run, I can choose a region, which is fine. Cloud Run delegates the build to Cloud Build, which apparently creates two buckets to make this happen. The unexpected behavior is that buckets aren't created in the region of the Cloud Run deployment, and instead default to multi-region US. How do I specify the region as "us-east1" so the cost of storage is absorbed by the "always free" tier? (Apparently US multi-region storage buckets store data in

Connect Google Cloud Run to MongoDB Atlas

隐身守侯 提交于 2020-07-05 10:43:48
问题 I'm evaluating a move from Google Kubernetes Engine to Google Cloud Run, to improve cost and resource efficiency within our company. I'm also in the process of transitioning our workflows from monolithic PHP and Ruby apps to a more nimble Node.js setup, using MongoDB. For a small organization like ours, I like the idea of managed services such as Google Cloud Run and MongoDB Atlas, however, I'm concerned about the security. In MongoDB Atlas, it seems the only real security measure is to

google cloud authentication with bearer token via nodejs

我怕爱的太早我们不能终老 提交于 2020-06-29 04:05:23
问题 My client has a GraphQL API running on Google cloud run. I have recieved a service account for authentication as well as access to the gcloud command line tool. When using gcloud command line like so: gcloud auth print-identity-token I can generate a token that can be used to make post requests to the api. This works and I can make successful post requests to the api from postman, insomnia and from my nodejs app. However, when I use JWT authentication with "googleapis" or "google-auth" npm

unable to run selenium chrome-driver on google-cloud-run

给你一囗甜甜゛ 提交于 2020-06-28 04:47:24
问题 I have a docker container that runs a working selenium chrome driver script, however when the same image is deployed to Google Cloud Run I encounter the following error. webdriver.Chrome('/home/vmagent/app/chromedriver', chrome_options=self.options) File "/env/lib/python3.7/site-packages/selenium/webdriver/chrome/webdriver.py", line 81, in __init__ desired_capabilities=desired_capabilities) File "/env/lib/python3.7/site-packages/selenium/webdriver/remote/webdriver.py", line 157, in __init__

unable to run selenium chrome-driver on google-cloud-run

百般思念 提交于 2020-06-28 04:47:08
问题 I have a docker container that runs a working selenium chrome driver script, however when the same image is deployed to Google Cloud Run I encounter the following error. webdriver.Chrome('/home/vmagent/app/chromedriver', chrome_options=self.options) File "/env/lib/python3.7/site-packages/selenium/webdriver/chrome/webdriver.py", line 81, in __init__ desired_capabilities=desired_capabilities) File "/env/lib/python3.7/site-packages/selenium/webdriver/remote/webdriver.py", line 157, in __init__

Cloud Run Request Limit

风格不统一 提交于 2020-06-23 12:41:09
问题 Currently, Cloud Run has a request limit of 32 Mb per request, which makes it impossible to upload files like videos (which placed with no changes to GCP Storage). Meantime All Quotas page doesn't list this limitation as the one you can request an increase from support. So question is - does anyone know how to increase this limit or how to make it possible (uploading video and bigger files) to Cloud Run with given limitation? 回答1: Google recommended best practice is to use Signed URLs to

Google Cloud Run security concerns

三世轮回 提交于 2020-05-31 07:08:01
问题 I testing Google Cloud Run and I have some security concerns. Let's say I process a user input with a binary program. What if the program is vulnerable and malicious code injected into the container. The attacker would be able to access my database or storage or any resource the container has the permissions to access. The question is: is this a genuine concern and how do I prevent it? The best idea I have is to put another container inside that just holds the potentially vulnerable binary.

Google Cloud Run security concerns

僤鯓⒐⒋嵵緔 提交于 2020-05-31 07:07:51
问题 I testing Google Cloud Run and I have some security concerns. Let's say I process a user input with a binary program. What if the program is vulnerable and malicious code injected into the container. The attacker would be able to access my database or storage or any resource the container has the permissions to access. The question is: is this a genuine concern and how do I prevent it? The best idea I have is to put another container inside that just holds the potentially vulnerable binary.