Creating Application Containers with Google Cloud Buildpacks [APPRUN] Reviews

Sora T. · Reviewed over 3 years ago

SHI Y. · Reviewed over 3 years ago

Plato P. · Reviewed over 3 years ago

Anders H. · Reviewed over 3 years ago

Marcelo G. · Reviewed over 3 years ago

Prabakaran A. · Reviewed over 3 years ago

Mike S. · Reviewed over 3 years ago

Sebastian C. · Reviewed over 3 years ago

I prefer docker

Nopporn P. · Reviewed over 3 years ago

Rosie S. · Reviewed over 3 years ago

Romer A. · Reviewed over 3 years ago

Filip L. · Reviewed over 3 years ago

Conor T. · Reviewed over 3 years ago

Tiemoko D. · Reviewed over 3 years ago

G Hemanth K. · Reviewed over 3 years ago

Matt D. · Reviewed over 3 years ago

AMITAVA G. · Reviewed over 3 years ago

Venugopal H. · Reviewed over 3 years ago

Ana L. · Reviewed over 3 years ago

Python Build failed. Error message(the last part) is below: Creating Application Containers with Google Cloud Buildpacks [APPRUN] 45 minutes 5 Credits CBL391 Google Cloud Self-Paced Labs Objectives In this lab, you learn to: Build a sample application with pack and the Google Cloud Buildpacks builder. Deploy the resulting container image to Cloud Run. Deploy the same image again, this time using Cloud Run (which uses Google Cloud Buildpacks) to perform the -build and package the container image for you. Overview In this lab, you learn about Google Cloud buildpacks, which allow developers to create containerized applications and deploy them without the need to install Docker locally, or create a Dockerfile. You will then take the same image and learn to deploy it directly on Cloud Run, allowing Cloud Run to do the building for you. Setup and Requirements For each lab, you get a new GCP project and set of resources for a fixed time at no cost. Make sure you signed into Qwiklabs using an incognito window. Note the lab's access time (for example, img/time.png and make sure you can finish in that time block. There is no pause feature. You can restart if needed, but you have to start at the beginning. When ready, click img/start_lab.png. Note your lab credentials. You will use them to sign in to Cloud Platform Console. img/open_google_console.png Click Open Google Console. Click Use another account and copy/paste credentials for this lab into the prompts. If you use other credentials, you'll get errors or incur charges. Accept the terms and skip the recovery resource page. Do not click End Lab unless you are finished with the lab or want to restart it. This clears your work and removes the project. How to start your lab and sign in to the Console Click the Start Lab button. If you need to pay for the lab, a pop-up opens for you to select your payment method. On the left is a panel populated with the temporary credentials that you must use for this lab. Open Google Console Copy the username, and then click Open Google Console. The lab spins up resources, and then opens another tab that shows the Choose an account page. Tip: Open the tabs in separate windows, side-by-side. On the Choose an account page, click Use Another Account. Choose an account The Sign in page opens. Paste the username that you copied from the Connection Details panel. Then copy and paste the password. Important: You must use the credentials from the Connection Details panel. Do not use your Qwiklabs credentials. If you have your own GCP account, do not use it for this lab (avoids incurring charges). Click through the subsequent pages: Accept the terms and conditions. Do not add recovery options or two-factor authentication (because this is a temporary account). Do not sign up for free trials. After a few moments, the GCP console opens in this tab. Note: You can view the menu with a list of GCP Products and Services by clicking the Navigation menu at the top-left, next to “Google Cloud Platform”. Cloud Console Menu Activate Google Cloud Shell Google Cloud Shell is a virtual machine that is loaded with development tools. It offers a persistent 5GB home directory and runs on the Google Cloud. Google Cloud Shell provides command-line access to your GCP resources. In GCP console, on the top right toolbar, click the Open Cloud Shell button. Cloud Shell icon Click Continue. cloudshell_continue.png It takes a few moments to provision and connect to the environment. When you are connected, you are already authenticated, and the project is set to your PROJECT_ID. For example: Cloud Shell Terminal gcloud is the command-line tool for Google Cloud Platform. It comes pre-installed on Cloud Shell and supports tab-completion. You can list the active account name with this command: gcloud auth list Copied! Output: Credentialed accounts: - <myaccount>@<mydomain>.com (active) Example output: Credentialed accounts: - google1623327_student@qwiklabs.net You can list the project ID with this command: gcloud config list project Copied! Output: [core] project = <project_ID> Example output: [core] project = qwiklabs-gcp-44776a13dea667a6 Full documentation of gcloud is available on Google Cloud gcloud Overview . Reference Basic Linux Commands Below you will find a reference list of a few very basic Linux commands which may be included in the instructions or code blocks for this lab. Command --> Action . Command --> Action mkdir (make directory) create a new folder . cd (change directory) change location to another folder ls (list ) list files and folders in the directory . cat (concatenate) read contents of a file without using an editor apt-get update update package manager library . ping signal to test reachability of a host mv (move ) moves a file . cp (copy) makes a file copy pwd (present working directory ) returns your current location . sudo (super user do) gives higher administration privileges Task 1. Enable the Cloud Run API and configure your Shell environment From Cloud Shell, enable the Cloud Run API : gcloud services enable run.googleapis.com Copied! If you are asked to authorize the use of your credentials, do so. You should then see a successful message similar to this one: Operation "operations/acf.cc11852d-40af-47ad-9d59-477a12847c9e" finished successfully. Copied! Note: you can also enable the API using the APIs & Services section of the console. Set the compute region gcloud config set compute/region us-central1 Copied! Task 2. List the pack CLI commands The pack CLI has already been installed on your lab account. To see the list of pack commands available to you, open your cloud shell terminal and type pack. You should see output similar to the example below: cli-commands.png Scan the list. Which of the commands you see in your output do you think will be needed to generate a container image from your source code? rebase check build inspect-image version Task 3. Clone the Buildpack sample repository Google Cloud Buildpack helps developers focus on writing code, not on containerizing it. Buildpack supports the following languages: Java, Node, Go, Python, and .NET (C#). Google provides a Buildpack Repository containing sample code you can use to practice using Buildpack to easily containerize and deploy applications. To use the provided sample applications in the language of your choice, you will first need to clone the Buildpack repository and then select a sample to build with the pack build command. Clone the buildpack-samples repository Clone the buildpacks samples repository to your local directory using the command below: git clone https://github.com/GoogleCloudPlatform/buildpack-samples.git Copied! Select your sample application Copy code from the language of your choice, shown in the list in the table below. Use this code in the cloud shell to build an application container. (You only need to create one container in one of these languages for the purposes of this lab.) JavaScript Python Go Java (Gradle) Java (Maven) DotNet cd buildpack-samples/sample-node pack build --builder=gcr.io/buildpacks/builder sample-node Copied! Run your new build container in Docker Run the appropriate section from the command below to bind the sample app created in the previous step to port 8080, so that it can be accessed via the browser. JavaScript Python Go Java (Gradle) Java (Maven) DotNet docker run -it -e PORT=8080 -p 8080:8080 sample-java-gradle Copied! In the Cloud Shell window, click on the Web preview icon and select Preview on port 8080. A new browser will open showing the "hello, world" message. Press Ctrl+C to stop the application. Task 4. Build and run your sample App on Cloud Run In the tasks above, we have built a container image locally using pack. After this, the next step would generally be pushing the container to Artifact Registry and then deploy to Cloud Run. However, it is also possible to have Cloud Run do all of the building and deployment for you. Use the one-step gcloud command to deploy your container: gcloud beta run deploy --source . Copied! When prompted: Confirm the service name by pressing Enter. Choose us-central1 region. If asked to allow unauthenticated invocations, type Y and press Enter. Wait a few minutes until the deployment is complete. The output should look similar to the below example: Done. Service [sample-node] revision [sample-node-00001-woz] has been deployed and is serving 100 percent of traffic. Service URL: https://sample-node-z2caq24usq-uc.a.run.app Copied! End your lab When you have completed your lab, click End Lab. Google Cloud Skills Boost removes the resources you’ve used and cleans the account for you. You will be given an opportunity to rate the lab experience. Select the applicable number of stars, type a comment, and then click Submit. The number of stars indicates the following: 1 star = Very dissatisfied 2 stars = Dissatisfied 3 stars = Neutral 4 stars = Satisfied 5 stars = Very satisfied You can close the dialog box if you don't want to provide feedback. For feedback, suggestions, or corrections, please use the Support tab. Congratulations! You have completed this lab! Next Steps / Learn More For more information on building a stateless HTTP container suitable for Cloud Run from code source and pushing it to Container Registry, see: Developing Cloud Run services Building Containers Manual Last Updated June 10, 2021 Lab Last Tested June 10, 2021 Copyright 2021 Google LLC All rights reserved. Google and the Google logo are trademarks of Google LLC. All other company and product names may be trademarks of the respective companies with which they are associated.

kichi d. · Reviewed over 3 years ago

There was a build error, reported through feedback

Billy B. · Reviewed over 3 years ago

Bharath V. · Reviewed over 3 years ago

Nagesh R. · Reviewed over 3 years ago

node 12.11.0 is unavailable, please update to 14.17.0

Mark T. · Reviewed almost 4 years ago

There is an error when trying to run the second code from task 3

David H. · Reviewed almost 4 years ago