Rapids Runs: One-Off and Scheduled Jobs From Your Container's Image
Run your Rapids container's image exactly once, on demand or on a cron schedule, for a migration, backfill or maintenance script, without touching the replicas that serve your traffic.
What's changed
- Start a run from the new Runs tab on your container's page, from the API or with the danube CLI; it uses your container's image and environment, and you can add per-run environment variables, choose an image tag and set a timeout of up to an hour
- Only one run is active per container at a time, apart from the replicas serving traffic, so a migration never runs twice or concurrently
- Schedule runs with a standard cron expression in your own timezone; a run that comes due while the previous one is still going is skipped and recorded, not stacked
- Follow a run's log live in a drawer, and read the last lines of its output for 10 days after it finishes
- The Command field splits arguments the way a shell does, so a quoted argument stays in one piece, and leaving it empty asks you to confirm before the image's own startup command runs
- A run is billed like one of your container's replicas, at the same vCPU-second and GiB-second rates with the same monthly free tier, from the moment it starts until it exits, with no separate run charge
- Get a webhook when a run succeeds or fails, and call your own container from a run through its internal URL