ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
My most recent builds with GCloud all started failing recently and I am not really sure why. I keep getting 404 errors from the build attempting to find an image that doesn't exist. Sample error: Already have image (with digest): us.gcr.io/gae-runtimes/buildpacks/google-gae-22/python/builder:python_20230925_RC00 ===> ANALYZING ERROR: failed to initialize
Asked · Sep 26
answered · Sep 28
I have a java spring boot backend app, that I am trying to hook up to Firebase Cloud Messages. I have an android app that uses firebase and I am trying to use this backend to push notifications. I've generated a private key from firebase console project settings, placed the json file - and the following worked LOCALLY perfectly: try { FirebaseOptions options
I´m trying to publish the html code from one cloud source repository to a public storage bucket in gcp through a cloud build trigger . However , I get the following error in the build each time I push to the master branch. generic::invalid_argument: generic::invalid_argument: if 'build.service_account' is specified, the build must either (a) specify 'build.l
Assume I have a cloudbuild.yaml file like the one below. Also assume that I can run and deploy the container in question manually when using gcloud for the separate functionalities (building and running). When deploying, the third step is resulting in the error ERROR: (gcloud.run.deploy) PERMISSION_DENIED: The caller does not have permission steps: # Build t
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 regio
I have a Google App Engine app, which connects to Google Cloud Storage. I noticed that the amount of data stored was unreasonably high (4.01 GB, when it should be 100MB or so). So, I looked at how much each bucket was storing, and I found that there was an automatically created bucket called us.artificats. that was taking up most of the space. I looked insid
firebase