# Your stack on Cloud Run

> Getting Node, Python, Rails, Go and Rust apps into a Cloud Run container: buildpacks or a Dockerfile, the build, the start and each stack's traps.

<https://exodus.elim.io/blog/topic/stacks>

These guides are about the language and framework an app is written in. They show how Node, Python, Rails, Go and Rust apps get into a Cloud Run container, with buildpacks or a Dockerfile, what each stack needs at build time and at start, the traps that are particular to each one, and what the start time means for the bill.

- [Node, Python, Rails and Go on Cloud Run: the container and the traps of each stack](https://exodus.elim.io/blog/node-python-rails-and-go-on-cloud-run.md): The container each of Node, Python, Rails and Go needs on Cloud Run, and the traps we reproduced: dropped requests on shutdown, one-at-a-time gunicorn, port 80, and Go's CPU count.
- [Rust on Cloud Run: the container, the build, the first second, and the bill](https://exodus.elim.io/blog/rust-on-cloud-run.md): How we run Rust on Cloud Run: $PORT and SIGTERM, a two-stage Dockerfile for an 11 MB image, where to compile, why 256 MiB means the first generation, start times, and three setups' bills.
- [Buildpacks or a Dockerfile: how to get your code into a Cloud Run container](https://exodus.elim.io/blog/buildpacks-or-a-dockerfile.md): One command builds your Cloud Run container with Google's buildpacks or your own Dockerfile. What each does, what it costs, who patches the OS, what breaks, and the commands for both.