rwx image push

Push an RWX task to an OCI reference

Usage

rwx image push  --to  [flags]

Description

The push command pushes a completed RWX task as a container image to one or more OCI-compliant container registries.

Authentication

You'll need to be authenticated to the registry you want to push to before running this command. The authentication should be configured in your local Docker environment or within the RWX run where you're executing the push.

Execution Model

The local machine that initiates the rwx image push does not download or upload any image data. To achieve fast performance, the actual push happens via an RWX run. This means:

  • Your local machine only coordinates the operation
  • The image data is transferred directly from RWX to your registry
  • Network bandwidth on your local machine is not consumed

Examples

Push a task to a single registry:

rwx image push bf3c1467e60eb5601ef2a43b840a0d96 \
  --to 123456789012.dkr.ecr.us-east-2.amazonaws.com/your_repository:your_tag

Push to multiple tags at once:

rwx image push bf3c1467e60eb5601ef2a43b840a0d96 \
  --to 123456789012.dkr.ecr.us-east-2.amazonaws.com/your_repository:latest \
  --to 123456789012.dkr.ecr.us-east-2.amazonaws.com/your_repository:v1.2.3

Push without waiting for completion:

rwx image push bf3c1467e60eb5601ef2a43b840a0d96 \
  --to registry.example.com/myimage:latest \
  --no-wait

Push and open the run in your browser:

rwx image push bf3c1467e60eb5601ef2a43b840a0d96 \
  --to registry.example.com/myimage:latest \
  --open

Arguments

<task-id>

(required) The ID of the RWX task to push. This is the task that contains the filesystem you want to push as a container image.

Options

--to <reference>

(required) The qualified OCI reference to push the image to. This should be the full registry path including the repository and tag (e.g., registry.example.com/repository:tag). Can be specified multiple times to push to multiple locations.

--json

Output JSON instead of human-readable text. Useful for scripting and automation.

--no-wait

Do not wait for the push to complete. The CLI will initiate the push and exit immediately without blocking.

--open

Open the push run URL in your default browser once the push starts. This allows you to monitor the push progress in the RWX web UI.