[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC):2025-09-02。"],[],[],null,["# Migrate an existing web service\n\nThis guide shows how to prepare a web service to run in a container on\nCloud Run. It does not cover data migration.\n\nIdentify the port your code is listening on\n-------------------------------------------\n\nYour service should listen for requests on a specific port. You must identify\nthis port and [configure Cloud Run to send requests to the same port](/run/docs/configuring/services/containers#command-line).\n\nThis is the same port you would use when invoking your service on your local\nmachine. For example, if to test your code you open `localhost:3000`, then [set\nthe container port](/run/docs/configuring/services/containers#command-line) to\n`3000` in Cloud Run.\n\nCloud Run defaults to sending requests to `8080`.\nThe value of the port to which requests are sent is always available in the\n`PORT` environment variable. It is a best practice for your code to listen on\nthe value defined by the `PORT` environment variable if possible.\n\nRemove reliance on local filesystem for persistent storage\n----------------------------------------------------------\n\nCheck your application code for reliance on local filesystems, and replace it\nwith file storage on [Cloud Storage](/storage) or data storage such as\n[Firestore](/firestore) or [Cloud SQL](/sql).\n\nAdd a `Dockerfile`\n------------------\n\nIn order to wrap your service in a container, you should use a Dockerfile to\ndefine the operating environment. The\n[build and deploy quickstart](/run/docs/quickstarts#build-and-deploy-a-web-service)\nshows some basic Dockerfiles you can use to get started.\n\nRead more about customizing your `Dockerfile` on the [Developing your service](/run/docs/developing#add-dockerfile)\npage.\n\nTune for concurrency and memory limits\n--------------------------------------\n\nLearn more about [how concurrency works](/run/docs/about-concurrency)\nthen optimize your service concurrency support in [development tips for tuning concurrency](/run/docs/tips#tuning-concurrency)\n\nMake sure your [memory limit](/run/docs/configuring/services/memory-limits) is high enough\nfor your application to run, including capacity for any temporary file storage\nyour service requires.\n\nSend logs to stdout, stderr, or /var/log\n----------------------------------------\n\nCloud Run automatically uses Google Cloud Observability to aggregate and\nreview your logs, as described in the [logging page](/run/docs/logging)."]]