google-container-builder

Passing files from Google Cloud Container Builder to Docker build task

阅读更多关于 Passing files from Google Cloud Container Builder to Docker build task

问题 Context A Ruby on Rails application built with Container Builder destined for App Engine. We require bundler to be able to install dependencies from a private git repository using a SSH key. The SSH Keys come from a secure bucket where they pass through KMS for decryption. Those steps are fine. However, the final step to build the container with Docker fails nothing able to access the SSH key. I do not have any previous extensive experience with Docker so I assume this is a simple issue.

Google cloud container builder not always triggering from bitbucket

阅读更多关于 Google cloud container builder not always triggering from bitbucket

问题 I have build triggers set up in the Google Cloud Container Builder that are set to trigger on specific branches and use the cloudbuild.yml config in the repo. For about the first day that I pushed commits to any of these branches, it triggered a container build and completed successfully. Since then, the triggers have only worked intermittently. Sometimes Google Cloud Container Builder doesn't detect the commit at all (I have checked the commit is in bitbucket and the commit is on the right

Cloud Container Builder, ZIP does not support timestamps before 1980

阅读更多关于 Cloud Container Builder, ZIP does not support timestamps before 1980

问题 I'm trying the following tutorial. Automatic serverless deployments with Cloud Source Repositories and Container Builder But I got the error below. $ gcloud container builds submit --config deploy.yaml . BUILD Already have image (with digest): gcr.io/cloud-builders/gcloud ERROR: (gcloud.beta.functions.deploy) Error creating a ZIP archive with the source code for directory .: ZIP does not support timestamps before 1980 ERROR ERROR: build step 0 "gcr.io/cloud-builders/gcloud" failed: exit

cloudbuil.yaml does not unmarshall when using base64-encoded value on build trigger

阅读更多关于 cloudbuil.yaml does not unmarshall when using base64-encoded value on build trigger

问题 On my cloudbuild.yaml definition, I used to have a secrets section to get environment values from Google KMS. The secretEnv fields had keys mapping to 'encrypted + base64-encoded' values: ... secrets: - kmsKeyName: <API_PATH> secretEnv: <KEY>: <ENCRYPTED+BASE64> I've tried to put this value on a substitution instead, which is replaced when a build trigger is used: ... secrets: - kmsKeyName: <API_PATH> secretEnv: <KEY>: ${_VALUE} With that I intend to keep the file generic. However, the build

Google Cloud Platform pipeline/container builder issue building docker image using COPY or ADD command for Spring Boot Java Application

阅读更多关于 Google Cloud Platform pipeline/container builder issue building docker image using COPY or ADD command for Spring Boot Java Application

问题 Created basic HelloWorld microservice using Spring Boot (2.1.3), Java 8, Maven. pom.xml has maven plugin entry like below <plugin> <groupId>org.springframework.boot</groupId> <artifactId>spring-boot-maven-plugin</artifactId> <configuration> <mainClass>com.example.HelloWorldApplication</mainClass> </configuration> </plugin> Dockerfile looks like below FROM openjdk:8 VOLUME /tmp ADD target/helloworld.jar helloworld.jar EXPOSE 8081 ENTRYPOINT ["java","-jar","helloworld.jar"] Created image on

Google Container Builder: How to install govendor dependencies during build step?

阅读更多关于 Google Container Builder: How to install govendor dependencies during build step?

问题 I am trying to use Google Cloud Container Builder to automate the building of my containers using GCP Build Triggers My code is in Go, and I have a vendor folder in my project root which contains all of my Go dependencies (I use govendor ). However, this vendor folder is NOT checked in to source control. I have a cloudbuild.yaml file where I first build my Go source into a main executable, and then build a Docker image using this executable. Container Builder ensures these build steps have

Google Cloud Platform pipeline/container builder issue building docker image using COPY or ADD command for Spring Boot Java Application

阅读更多关于 Google Cloud Platform pipeline/container builder issue building docker image using COPY or ADD command for Spring Boot Java Application

Created basic HelloWorld microservice using Spring Boot (2.1.3), Java 8, Maven. pom.xml has maven plugin entry like below <plugin> <groupId>org.springframework.boot</groupId> <artifactId>spring-boot-maven-plugin</artifactId> <configuration> <mainClass>com.example.HelloWorldApplication</mainClass> </configuration> </plugin> Dockerfile looks like below FROM openjdk:8 VOLUME /tmp ADD target/helloworld.jar helloworld.jar EXPOSE 8081 ENTRYPOINT ["java","-jar","helloworld.jar"] Created image on local machine using command docker build . -t helloworld:v1 Verified by creating container out of it.