Index of every page on this site: llms.txt
All skills
rivet-dev avatar

/rivet-deploy-image

@3b027b3 official
by Rivetrivet-dev/skills53 stars
14
Run it yourself

Deploy a Docker image to a Rivet Cloud cluster through the Rivet MCP server, or roll a cluster back to an earlier build. Use when asked to deploy, ship, release, or roll back an app on a Rivet cluster and a shell with Docker is available.

Use this Skill: https://skilld.dev/gh/rivet-dev/skills/rivet-deploy-image

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

referencesrollout.md

≈545 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Rollout steps, errors, and rollback

What rivet.deploy.rollout returns

{ done, step, build_id, build_status?, region?, pool?, status?: { state, message, action_needed }, endpoints? }
step Meaning What to do
verifying_build The upload is being checked against the size and digest it was prepared with. build_status is uploading or completing. Call again with the same arguments.
rolling_out The runner pool has been pointed at the build and is not ready yet. status.message says what is changing. When status.action_needed is true, the build itself is failing and status.message says why. Call again with the same arguments, or fix the app and deploy a new build when status.action_needed is true.
ready The pool runs the build, its status.state is ready, and done is true. Stop and report endpoints.

Arguments

  • region is only needed when the cluster has several. With exactly one region it is chosen for you.
  • pool defaults to default. A pool that does not exist yet is created with an empty allowlist. An existing pool keeps the allowlist it has.

Errors

Error Cause What to do
deploy/build_failed The uploaded bytes did not match content_length and content_md5. Measure the tarball again, call rivet.deploy.prepare, and upload again.
deploy/build_expired, deploy/build_deleting The build can no longer be deployed, for example because it was never uploaded before expires_at. Call rivet.deploy.prepare for a new build.
deploy/region_required The cluster has several regions, or none. The message lists the regions. Pass one as region, or add a region first when there are none.

A failed upload command means nothing was deployed. Run it again while the URL is still valid, or prepare a new build.

Rolling back

Call rivet.deploy.rollout with an earlier build_id, and repeat it until done is true exactly as for a deploy. Nothing is rebuilt or uploaded. rivet.cloud.v2.builds.list lists a cluster's builds newest first with their status, and only a ready build can be rolled to.

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts26d3 checks · Risk SAFE
  • Gen Agent Trust Hub26d

    The skill facilitates Docker image deployment to Rivet Cloud using standard shell commands and vendor-specific APIs. It follows security best practices such as recommending the exclusion of environment files from image builds.

  • Socket28d

    No alerts

  • Snyk28d

    Risk: LOW · No issues

Signed by skilld at 3b027b3. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated last month
metadata
{
  "rivet-requires": "rivet.deploy.prepare rivet.deploy.rollout"
}

README badge

README badge for rivet-dev/skills/rivet-deploy-image