[[["์ดํดํ๊ธฐ ์ฌ์","easyToUnderstand","thumb-up"],["๋ฌธ์ ๊ฐ ํด๊ฒฐ๋จ","solvedMyProblem","thumb-up"],["๊ธฐํ","otherUp","thumb-up"]],[["์ดํดํ๊ธฐ ์ด๋ ค์","hardToUnderstand","thumb-down"],["์๋ชป๋ ์ ๋ณด ๋๋ ์ํ ์ฝ๋","incorrectInformationOrSampleCode","thumb-down"],["ํ์ํ ์ ๋ณด/์ํ์ด ์์","missingTheInformationSamplesINeed","thumb-down"],["๋ฒ์ญ ๋ฌธ์ ","translationIssue","thumb-down"],["๊ธฐํ","otherDown","thumb-down"]],["์ต์ข ์ ๋ฐ์ดํธ: 2025-09-04(UTC)"],[[["\u003cp\u003eGoogle Cloud's buildpacks are an open-source project that transforms application source code into production-ready container images, based on the Cloud Native Buildpack specification.\u003c/p\u003e\n"],["\u003cp\u003eBuildpacks are responsible for language components or tools, and are grouped into builders that analyze code and generate deployable container images.\u003c/p\u003e\n"],["\u003cp\u003eGoogle Cloud Serverless products use buildpacks to package code into runnable containers, and the process is fully managed on Cloud Run functions and App Engine.\u003c/p\u003e\n"],["\u003cp\u003eBuilders and buildpacks are pre-configured to handle the build process and automatically detect the programming language, supporting multiple languages.\u003c/p\u003e\n"],["\u003cp\u003eBuildpacks can be used to build both applications/services and functions, and a \u003ccode\u003eProcfile\u003c/code\u003e can define the startup process for containers, being mandatory for some languages like Python.\u003c/p\u003e\n"]]],[],null,["# Google Cloud's buildpacks is an\n[open-source project](https://github.com/GoogleCloudPlatform/buildpacks)\nthat takes your application source code and transforms it into production-ready\ncontainer images. The buildpacks published by Google Cloud implement\nthe\n[Cloud Native Buildpack specification](https://buildpacks.io/)\nand are designed to help you build and configure containers that you can\ndeploy to Google Cloud.\n\nA buildpack is typically responsible for a language\ncomponent, toolchain, or app component; such as Python, `pip`, or a web server.\nBuildpacks are grouped together into collections called\n[builders](/docs/buildpacks/builders) that can analyze project source code,\ncreate a build plan, and generate a container image that is ready for deployment.\n\nContainerization with buildpacks\n--------------------------------\n\nWhen you deploy to and serve your application (service) or function on the\n[Google Cloud Serverless](https://cloud.google.com/serverless) products,\nyour code gets packaged into a runnable container using buildpacks.\nOn Cloud Run, you have the option to deploy a pre-built container or\n[deploy your source code](https://cloud.google.com/run/docs/deploying-source-code)\nto let Cloud Run manage the container build. On Cloud Run functions and\nApp Engine, the containerization process is fully-managed, meaning that when\nyou deploy your source code, all the container image packaging and converting\nis done for you.\n\nEach container image gets built with all the components needed for running your\ndeployment, including source code, system and library dependencies, configuration\ndata, and static assets. By default, the Google Cloud Serverless products\nuse the same underlying services, including Cloud Build for the deployment\npipeline, and either Container Registry or Artifact Registry for container image storage\nand management.\n\nWhen using Google Cloud's buildpacks:\n\n- Builders and buildpacks are pre-configured to handle the build process and create a runnable container image for you.\n- Buildpacks support [multiple programming languages](/docs/buildpacks/builders) and automatically detects which lanaguage is used in your source code.\n- You can [customize and extend buildpacks](/docs/buildpacks/build-run-image) to install additional system dependencies. However, the default builder can handle the common tasks required by your programming language, including installing dependencies from the language's package repository and using the language's common dependency file.\n\nUse buildpacks to containerize your code\n----------------------------------------\n\nBuildpacks can be used locally or remotely to:\n\n- [Build an application or service](/docs/buildpacks/build-application)\n- [Build a function](/docs/buildpacks/build-function)\n\nFor programming languages that exclude a standard ways to start an application,\nyou can use a `Procfile` to define the process to invoke when a container starts.\nA `Procfile` can be used to override the default start process for any\nbuildpacks type, but is mandatory for some, including\n[Python](https://cloud.google.com/docs/buildpacks/python#application_entrypoint).\n\nWhat's next\n-----------\n\n- [Builders](/docs/buildpacks/builders)\n- [Build an application](/docs/buildpacks/build-application)\n- [Build a function](/docs/buildpacks/build-function)\n- Learn about [Cloud Native Buildpacks](https://buildpacks.io/docs/for-platform-operators/concepts/)"]]
