Create and execute a job in Cloud Run

This page shows you how to create a job in Cloud Run using a sample container, execute the job, and view logs for the job.

Before you begin

  1. Sign in to your Google Cloud account. If you're new to Google Cloud, create an account to evaluate how our products perform in real-world scenarios. New customers also get $300 in free credits to run, test, and deploy workloads.

  2. In the Google Cloud console, on the project selector page, select or create a Google Cloud project.

    Go to project selector

  3. Make sure that billing is enabled for your Google Cloud project .

    4.

  4. In the Google Cloud console, on the project selector page, select or create a Google Cloud project.

    Go to project selector

  5. Make sure that billing is enabled for your Google Cloud project .

    6.

Create a job

To create a job:

  1. In the Google Cloud console, go to the Cloud Run page:

    Go to Cloud Run

  2. Click Deploy containerand select Jobto open the Create jobpage.

  3. Click Test with a sample container.

  4. In the Regionpulldown menu, select the region where you want to run the job.

  5. Click Createto create the job.

The job is created and is ready to be executed.

Execute the job

After you create a job, you can execute it:

  1. In the Jobstab, click the job you just created to open the Job detailspage.

  2. Click Execute.

  3. Logs for the job are available as soon as the job execution starts. Click the Logstab to view the logs for the job.

Congratulations! You have just created and executed a job in Cloud Run.

Cloud Run locations

Cloud Run is regional, which means the infrastructure that runs your Cloud Run services is located in a specific region and is managed by Google to be redundantly available across all the zones within that region .

Meeting your latency, availability, or durability requirements are primary factors for selecting the region where your Cloud Run services are run. You can generally select the region nearest to your users but you should consider the location of the other Google Cloud products that are used by your Cloud Run service. Using Google Cloud products together across multiple locations can affect your service's latency as well as cost.

Cloud Run is available in the following regions:

Subject to Tier 1 pricing

  • asia-east1 (Taiwan)
  • asia-northeast1 (Tokyo)
  • asia-northeast2 (Osaka)
  • europe-north1 (Finland)leaf icon Low CO 2
  • europe-southwest1 (Madrid)leaf icon Low CO 2
  • europe-west1 (Belgium)leaf icon Low CO 2
  • europe-west4 (Netherlands)leaf icon Low CO 2
  • europe-west8 (Milan)
  • europe-west9 (Paris)leaf icon Low CO 2
  • me-west1 (Tel Aviv)
  • us-central1 (Iowa)leaf icon Low CO 2
  • us-east1 (South Carolina)
  • us-east4 (Northern Virginia)
  • us-east5 (Columbus)
  • us-south1 (Dallas)leaf icon Low CO 2
  • us-west1 (Oregon)leaf icon Low CO 2

Subject to Tier 2 pricing

  • africa-south1 (Johannesburg)
  • asia-east2 (Hong Kong)
  • asia-northeast3 (Seoul, South Korea)
  • asia-southeast1 (Singapore)
  • asia-southeast2 (Jakarta)
  • asia-south1 (Mumbai, India)
  • asia-south2 (Delhi, India)
  • australia-southeast1 (Sydney)
  • australia-southeast2 (Melbourne)
  • europe-central2 (Warsaw, Poland)
  • europe-west10 (Berlin)leaf icon Low CO 2
  • europe-west12 (Turin)
  • europe-west2 (London, UK)leaf icon Low CO 2
  • europe-west3 (Frankfurt, Germany)leaf icon Low CO 2
  • europe-west6 (Zurich, Switzerland)leaf icon Low CO 2
  • me-central1 (Doha)
  • me-central2 (Dammam)
  • northamerica-northeast1 (Montreal)leaf icon Low CO 2
  • northamerica-northeast2 (Toronto)leaf icon Low CO 2
  • southamerica-east1 (Sao Paulo, Brazil)leaf icon Low CO 2
  • southamerica-west1 (Santiago, Chile)leaf icon Low CO 2
  • us-west2 (Los Angeles)
  • us-west3 (Salt Lake City)
  • us-west4 (Las Vegas)

If you already created a Cloud Run service, you can view the region in the Cloud Run dashboard in the Google Cloud console .

What's next