Meta tags:

Headings (most frequently used words):

your, cloud, run, job, delete, with, on, and, the, roles, console, gcloud, gpu, accelerated, video, transcoding, ffmpeg, jobs, stay, organized, collections, save, categorize, content, based, preferences, objectives, costs, before, you, begin, prepare, application, create, storage, buckets, deploy, clean, up, what, next, required, repository, test, project, products, pricing, support, resources, engage, grant,

Text of the page (most frequently used words):
the (124), cloud (113), run (74), project (66), and (52), you (52), with (45), #create (42), your (41), google (37), for (34), deploy (33), service (32), gcloud (30), project_id (30), from (29), roles (27), job (25), overview (25), delete (24), storage (24), services (24), jobs (23), this (20), that (19), gpu (19), video (18), using (18), role (18), code (17), iam (17), container (16), location (16), build (16), resources (15), samples (14), select (14), region (14), worker (14), sample (13), use (13), replace (13), volume (13), grant (13), functions (13), following (12), name (12), account (12), pools (12), all (11), registry (11), encoding (11), tutorial (11), environment (11), configure (11), vpc (11), execute (10), add (10), projects (9), image (9), source (9), view (9), volumes (9), function (9), com (8), artifact (8), buckets (8), access (8), identity (8), best (8), practices (8), trigger (8), triggers (8), thumb (7), other (7), custom (7), console (7), repository (7), transcoded (7), memory (7), can (7), development (7), limits (7), requests (7), pub (7), sub (7), maximum (7), manage (6), need (6), are (6), java (6), created (6), steps (6), ffmpeg (6), bucket (6), application (6), required (6), enable (6), cli (6), gpus (6), migrate (6), agents (6), metrics (6), python (6), sign (5), about (5), send (5), might (5), these (5), click (5), instances (5), cost (5), file (5), type (5), store (5), videos (5), processing (5), get (5), permission (5), how (5), tools (5), security (5), networking (5), migration (5), network (5), traffic (5), node (5), eventarc (5), invoke (5), português (4), español (4), products (4), down (4), more (4), when (4), existing (4), also (4), any (4), billing (4), follow (4), test (4), mp4 (4), entrypoint (4), preprocessing (4), image_name (4), note (4), cpu (4), zonal (4), redundancy (4), retries (4), mount (4), binding (4), write (4), results (4), local (4), new (4), admin (4), set (4), usage (4), plan (4), selecting (4), resourcemanager (4), external (4), based (4), transcoding (4), management (4), containers (4), configuration (4), inference (4), direct (4), scaling (4), instance (4), health (4), variables (4), optimize (4), dependencies (4), events (3), github (3), system (3), pricing (3), see (3), understand (3), information (3), content (3), page (3), under (3), developers (3), deleting (3), have (3), instead (3), used (3), tasks (3), command (3), time (3), repositories (3), documentation (3), additional (3), logs (3), read (3), input (3), output (3), data (3), example (3), first (3), must (3), docker (3), nvidia (3), gserviceaccount (3), machine (3), doesn (3), policy (3), member (3), after (3), save (3), contains (3), git (3), prepare (3), address (3), user (3), permissions (3), complete (3), through (3), per (3), googleapis (3), apis (3), learn (3), install (3), free (3), costs (3), accelerated (3), guides (3), hosting (3), frameworks (3), monitoring (3), solutions (3), distributed (3), databases (3), introduction (3), web (3), mcp (3), log (3), secure (3), authenticate (3), connectors (3), host (3), optimization (3), autoscale (3), labels (3), secrets (3), checks (3), ephemeral (3), disk (3), cifs (3), smb (3), nfs (3), mounts (3), connect (3), firestore (3), concurrent (3), product (3), 한국어 (2), 日本語 (2), עברית (2), brasil (2), italiano (2), indonesia (2), français (2), américa (2), latina (2), deutsch (2), english (2), our (2), terms (2), site (2), youtube (2), started (2), release (2), support (2), last (2), updated (2), 2026 (2), utc (2), otherwise (2), licensed (2), its (2), license (2), feedback (2), explore (2), tutorials (2), next (2), want (2), document (2), work (2), job_name (2), executions (2), running (2), list (2), only (2), task (2), charges (2), deployed (2), encoded_cat (2), make (2), sure (2), cat (2), default (2), quota (2), pkg (2), dev (2), path (2), builds (2), already (2), directory (2), serviceaccount (2), before (2), clone (2), https (2), adding (2), typically (2), email (2), principal (2), basic (2), accounts (2), cloudbuild (2), editor (2), artifactregistry (2), administrator (2), request (2), owner (2), serviceusage (2), verify (2), enabled (2), config (2), creating (2), don (2), keep (2), procedure (2), finish (2), removing (2), associated (2), creator (2), which (2), projectcreator (2), require (2), specific (2), been (2), granted (2), init (2), initialize (2), provider (2), idp (2), federated (2), perform (2), world (2), users (2), sdk (2), languages (2), infrastructure (2), observability (2), industry (2), hybrid (2), multicloud (2), analytics (2), pipelines (2), compute (2), troubleshoot (2), oci (2), app (2), assisted (2), llm (2), execution (2), remote (2), server (2), adk (2), a2a (2), logging (2), prometheus (2), controls (2), static (2), shared (2), connector (2), private (2), automate (2), workflows (2), description (2), metadata (2), systems (2), capacity (2), rollbacks (2), pool (2), revisions (2), continuous (2), tags (2), timeout (2), testing (2), integrate (2), workflow (2), base (2), runtimes (2), images (2), configurations (2), http (2), serving (2), serve (2), returns (2), php (2), ruby (2), develop (2), cases (2), cross (2), reference (2), technology (2), areas (2), close (2), subscribe, newsletter, third, decade, climate, action, join, cookies, privacy, tech, twitter, blog, engage, training, certification, architecture, center, getting, status, notes, community, forums, contact, sales, marketplace, easy, easytounderstand, solved, problem, solvedmyproblem, otherup, hard, hardtounderstand, incorrect, incorrectinformationorsamplecode, missing, missingtheinformationsamplesineed, otherdown, tell, except, noted, details, registered, trademark, oracle, affiliates, policies, apache, creative, commons, attribution, demos, what, has, effects, future, preserve, urls, such, url, selected, inside, whole, appspot, ids, lost, done, everything, deleted, caution, stops, terminates, progress, locate, checkbox, incur, executing, one, executes, however, still, charged, storing, avoid, quickstart, clean, download, review, trancoded, requires, arguments, wait, args, vcodec, h264_nvenc, movflags, faststart, upload, encode, prompts, same, 32gi, max, readonly, inputs, outputs, true, uses, larger, reduce, submit, tag, highcpu, artifacts, format, exist, navigate, dockerfile, mounting, objectadmin, objectviewer, two, change, googlecloudplatform, retrieve, deployer, number, project_number, each, another, field, enter, identifier, principals, person_add, contain, shouldn, production, but, them, able, predefined, granting, folders, organizations, serviceaccountuser, serviceaccountcreator, repoadmin, ask, api, alternatively, automatically, receive, off, quotas, total, allocation, without, variable, export, then, likely, serviceusageadmin, evaluate, real, scenarios, customers, 300, credits, workloads, begin, generate, estimate, projected, eligible, trial, calculator, billable, components, successfully, accelerate, will, objectives, describes, transcode, low, priority, offline, categorize, preferences, stay, organized, collections, home, known, issues, troubleshooting, errors, gke, kubernetes, vmware, tanzu, spring, music, choose, compliant, strategy, foundry, heroku, aws, lambda, 1st, gen, engine, cookbook, vibe, coding, batch, fine, tune, llms, hugging, face, transformers, opencv, acceleration, gemma, models, ollama, browser, automation, servers, n8n, tracing, error, reporting, audit, opentelemetry, built, monitor, multi, tenant, platforms, untrusted, software, supply, chain, insights, constraints, customer, managed, encryption, keys, threat, detection, binary, authorization, protect, armor, iap, control, end, authentication, audiences, allow, public, design, mesh, restrict, endpoint, ingress, outbound, standard, dual, stack, ipv4, ipv6, register, ips, dns, pull, subscriptions, runners, kafka, autoscaler, scale, count, splits, background, checkpoints, stop, parallelism, scheduled, completion, event, driven, load, general, tips, grpc, database, routed, entries, into, call, push, subscription, asynchronous, series, part, schedule, asynchronously, websocket, chat, stream, websockets, webhook, target, automatic, updates, supported, language, manual, minimum, autoscaling, sandboxes, port, recommender, performance, gradual, rollouts, copy, frontend, proxying, nginx, session, affinity, failover, multiple, regions, assets, cdn, mapping, domains, compose, deployment, sources, codelabs, spanner, bigquery, net, compare, commands, within, package, containerize, shell, sveltekit, nuxt, angular, ssr, kotlin, agent, kit, streamlit, smolagents, langchain, gradio, fastapi, flask, hello, should, good, fit, runtime, contract, resource, model, discover, start, skip, main,

Text of the page (random words):
red vpc connector to direct vpc connectors in service projects connectors in host project static outbound ip address network security restrict endpoint ingress services use vpc service controls vpc sc cloud service mesh secure security design overview authenticate requests overview allow public access custom audiences authenticate developers service to service authenticate users end user authentication tutorial secure your resources access control with iam configure iap for cloud run introduction to service identity protect services with cloud armor use binary authorization use cloud run threat detection use customer managed encryption keys manage custom constraints for projects view software supply chain security insights secure cloud run services tutorial multi tenant platforms running untrusted code monitor and log monitoring and logging overview view built in metrics write prometheus metrics write opentelemetry metrics log and view logs audit logging error reporting use distributed tracing for services run ai solutions overview explore resources ai agents overview build and deploy a2a agents overview deploy a2a agents build and deploy adk agents build and deploy n8n agents mcp servers overview build and deploy a remote mcp server tools code execution browser automation inference with gpus overview services run llm inference on cloud run gpus with ollama run agents with gemma 4 models on cloud run run opencv on cloud run with gpu acceleration run llm inference on cloud run gpus with hugging face transformers js jobs fine tune llms using gpus with cloud run jobs run batch inference using gpus with cloud run jobs gpu accelerated video transcoding with ffmpeg ai assisted development and vibe coding introduction to cloud run for ai assisted developers cookbook migrate an existing web service from app engine from cloud run functions 1st gen from aws lambda from heroku from cloud foundry migration overview choose an oci compliant strategy migrate to oci containers migrate configuration sample migration spring music from vmware tanzu from a vm using migrate to containers from kubernetes to gke troubleshoot introduction troubleshoot errors local troubleshooting tutorial known issues samples all cloud run code samples all cloud run functions code samples code samples for all products ai and ml application development application hosting compute data analytics and pipelines databases distributed hybrid and multicloud industry solutions migration networking observability and monitoring security storage access and resources management costs and usage management infrastructure as code sdk languages frameworks and tools home documentation application hosting cloud run guides send feedback gpu accelerated video transcoding with ffmpeg on cloud run jobs stay organized with collections save and categorize content based on your preferences this tutorial describes how to transcode low priority offline videos using cloud run jobs objectives in this tutorial you will do the following create cloud storage buckets to store the videos for processing and to store the encoding results deploy a cloud run job using gpus to accelerate video transcoding run the job and make sure the video transcoded successfully costs in this document you use the following billable components of google cloud cloud build artifact registry cloud run to generate a cost estimate based on your projected usage use the pricing calculator new google cloud users might be eligible for a free trial before you begin 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 install the google cloud cli if you re using an external identity provider idp you must first sign in to the gcloud cli with your federated identity to initialize the gcloud cli run the following command gcloud init create or select a google cloud project roles required to select or create a project select a project selecting a project doesn t require a specific iam role you can select any project that you ve been granted a role on create a project to create a project you need the project creator role roles resourcemanager projectcreator which contains the resourcemanager projects create permission learn how to grant roles note if you don t plan to keep the resources that you create in this procedure create a project instead of selecting an existing project after you finish these steps you can delete the project removing all resources associated with the project create a google cloud project gcloud projects create project_id replace project_id with a name for the google cloud project you are creating select the google cloud project that you created gcloud config set project project_id replace project_id with your google cloud project name verify that billing is enabled for your google cloud project install the google cloud cli if you re using an external identity provider idp you must first sign in to the gcloud cli with your federated identity to initialize the gcloud cli run the following command gcloud init create or select a google cloud project roles required to select or create a project select a project selecting a project doesn t require a specific iam role you can select any project that you ve been granted a role on create a project to create a project you need the project creator role roles resourcemanager projectcreator which contains the resourcemanager projects create permission learn how to grant roles note if you don t plan to keep the resources that you create in this procedure create a project instead of selecting an existing project after you finish these steps you can delete the project removing all resources associated with the project create a google cloud project gcloud projects create project_id replace project_id with a name for the google cloud project you are creating select the google cloud project that you created gcloud config set project project_id replace project_id with your google cloud project name verify that billing is enabled for your google cloud project enable the cloud run artifact registry and cloud build apis roles required to enable apis to enable apis you need the serviceusage services enable permission if you created the project then you likely already have this permission through the owner role roles owner otherwise you can get this permission through the service usage admin role roles serviceusage serviceusageadmin learn how to grant roles gcloud services enable run googleapis com cloudbuild googleapis com artifactregistry googleapis com set your region as an environment variable export region region create a service account gcloud iam service accounts create video encoding request total nvidia l4 gpu allocation without zonal redundancy per project per region under cloud run admin api in the quotas and system limits page to complete this tutorial alternatively you can deploy a cloud run service to automatically receive a grant of 3 nvidia l4 gpu quota zonal redundancy off for a region required roles to get the permissions that you need to complete the tutorial ask your administrator to grant you the following iam roles on your project artifact registry repository administrator roles artifactregistry repoadmin cloud build editor roles cloudbuild builds editor cloud run admin roles run admin create service accounts roles iam serviceaccountcreator service account user roles iam serviceaccountuser for more information about granting roles see manage access to projects folders and organizations you might also be able to get the required permissions through custom roles or other predefined roles note iam basic roles might also contain permissions to complete the tutorial you shouldn t grant basic roles in a production environment but you can grant them in a development or test environment grant the roles console in the google cloud console go to the iam page go to iam select the project click person_add grant access in the new principals field enter your user identifier this is typically the email address that is used to deploy the cloud run service in the select a role list select a role to grant additional roles click add add another role and add each additional role click save gcloud to grant the required iam roles to your account on your project gcloud projects add iam policy binding project_id member principal role role replace project_number with your google cloud project number project_id with your google cloud project id principal with the account you are adding the binding for this is typically the email address that is used to deploy the cloud run service role with the role you are adding to the deployer account prepare your application to retrieve the code sample for use clone the sample repository to your local machine git clone https github com googlecloudplatform cloud run samples change to the directory that contains the cloud run sample code cd cloud run samples jobs video encoding create cloud storage buckets to store the videos for processing and to save the results of encoding create the following two cloud storage buckets create a bucket to store videos before processing gcloud storage buckets create gs preprocessing project_id location location replace the following project_id your project id location the cloud storage location grant the service account access to read from this bucket gcloud storage buckets add iam policy binding gs preprocessing project_id member serviceaccount video encoding project_id iam gserviceaccount com role roles storage objectviewer replace project_id with your project id create a bucket to store transcoded videos after processing gcloud storage buckets create gs transcoded project_id location location replace the following project_id your project id location the cloud storage location grant the service account access to read from and write to this bucket gcloud storage buckets add iam policy binding gs transcoded project_id member serviceaccount video encoding project_id iam gserviceaccount com role roles storage objectadmin replace project_id with your project id deploy a cloud run job create a cloud run job by using the dockerfile in the sample repository and mounting the buckets that you created navigate to the sample directory cd cloud run samples jobs video encoding create an artifact registry if the default cloud run registry doesn t already exist gcloud artifacts repositories create cloud run source deploy repository format docker location location replace location with the name of the location of the registry build the container image gcloud builds submit tag location docker pkg dev project_id cloud run source deploy image_name machine type e2 highcpu 32 replace the following project_id your project id location name of the location of the registry image_name name for the container image for example ffmpeg image cloud run uses a larger machine type to reduce build time deploy the job gcloud run jobs create video encoding job image location docker pkg dev project_id cloud run source deploy image_name region region memory 32gi cpu 8 gpu 1 gpu type nvidia l4 no gpu zonal redundancy max retries 1 service account video encoding project_id iam gserviceaccount com add volume name input volume type cloud storage bucket preprocessing project_id readonly true add volume mount volume input volume mount path inputs add volume name output volume type cloud storage bucket transcoded project_id add volume mount volume output volume mount path outputs replace the following project_id your project id region the name of the region note this must be the same region that you have gpu quota for image_name name for the container image for example ffmpeg image if this is the first time you deployed from source in this project cloud run prompts you to create a default artifact registry repository run the job to run the job follow these steps upload an example video to encode gcloud storage cp gs cloud samples data video cat mp4 gs preprocessing project_id run the job gcloud run jobs execute video encoding job region region wait args cat mp4 encoded_cat mp4 vcodec h264_nvenc cq 21 movflags faststart the entrypoint sh file requires an input file output file and any arguments to send to ffmpeg review the cloud run logs to make sure the video trancoded gcloud run jobs logs read video encoding job region region download the transcoded video gcloud storage cp gs transcoded project_id encoded_cat mp4 clean up to avoid additional charges to your google cloud account delete all the resources you deployed with this quickstart delete your repository cloud run only charges for the time your job executes however you might still be charged for storing the container image in artifact registry to delete artifact registry repositories follow the steps in delete repositories in the artifact registry documentation delete your job cloud run jobs only incur cost when a job task is executing to delete your cloud run job follow one of these steps console to delete a job in the google cloud console go to cloud run go to cloud run locate the job you want to delete in the jobs list and click its checkbox to select it click delete this terminates all the job executions in progress and all running container instances gcloud to delete a job run the following command gcloud run jobs delete job_name replace job_name with the name of the job delete your test project deleting your google cloud project stops billing for all resources in that project to release all google cloud resources in your project follow these steps caution deleting a project has the following effects everything in the project is deleted if you used an existing project for the tasks in this document when you delete it you also delete any other work you ve done in the project custom project ids are lost when you created this project you might have created a custom project id that you want to use in the future to preserve the urls that use the project id such as an appspot com url delete selected resources inside the project instead of deleting the whole project delete a google cloud project gcloud projects delete project_id what s next explore other cloud run demos tutorials and samples send feedback except as otherwise noted the content of this page is licensed under the creative commons attribution 4 0 license and code samples are licensed under the apache 2 0 license for details see the google developers site policies java is a registered trademark of oracle and or its affiliates last updated 2026 07 22 utc need to tell us more easy to understand easytounderstand thumb up solved my problem solvedmyproblem thumb up other otherup thumb up hard to understand hardtounderstand thumb down incorrect information or sample code incorrectinformationorsamplecode thumb down missing the information samples i need missingtheinformationsa...