Skip to content

docs: state image architecture as region-dependent, not absolute #1183

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
markbackman merged 1 commit into from
Aug 27, 2026
Merged

docs: state image architecture as region-dependent, not absolute #1183

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion api-reference/cli/cloud/docker.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -169,7 +169,9 @@ pipecat cloud docker build-push --no-latest

## Platform Support

All images are built for the `linux/arm64` platform, which is required for Pipecat Cloud deployments. This is automatically configured and cannot be changed.
`build-push` always builds for `linux/arm64`. This is automatically configured and cannot be changed.

The architecture an agent needs depends on the region it deploys to — Daily-hosted regions run `arm64`, which is what this command produces. To build for a different architecture, build and push the image yourself rather than through this command.

## Error Handling

Expand Down
14 changes: 9 additions & 5 deletions llms-full.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24807,7 +24807,7 @@ We recommend using FastAPI to create this route. Please refer to the base image
to your own container registry.
</Note>

Pipecat Cloud requires all images to be built to target Linux on ARM. This is the most common platform for cloud deployments.
An agent image has to be built for the architecture its region runs. Daily-hosted regions run Linux on ARM, so build for `linux/arm64`:

```bash
docker build --platform linux/arm64 -t my-agent:latest .
Expand Down Expand Up @@ -26224,7 +26224,9 @@ Check that your image repository is not rate limiting your pull requests. This c

> Image platform is not supported.

Ensure the image you are attempting to pull is supported by Pipecat Cloud. Currently, Pipecat Cloud only supports images for the `linux/arm64` platform.
The image's architecture has to match what the target region supports. Daily-hosted regions run `linux/arm64`, so an image built for `amd64` is rejected there.

Check what you built with `docker image inspect <image> --format '{{.Architecture}}'`, and rebuild with `--platform linux/arm64` if it doesn't match.

### PCC_IMAGE_PULL_UNKNOWN_ERROR

Expand Down Expand Up @@ -26925,8 +26927,8 @@ If you host images in your own container registry (e.g. Docker Hub, AWS ECR, GHC

<Note>
When deploying a pre-built image, you must provide an `image-credentials`
reference if the image is in a private registry. Pipecat Cloud requires images
built for `linux/arm64`.
reference if the image is in a private registry. Build for the architecture
your region runs — `linux/arm64` for Daily-hosted regions.
</Note>

## Using v1 with Docker Build
Expand Down Expand Up @@ -92236,7 +92238,9 @@ pipecat cloud docker build-push --no-latest

## Platform Support

All images are built for the `linux/arm64` platform, which is required for Pipecat Cloud deployments. This is automatically configured and cannot be changed.
`build-push` always builds for `linux/arm64`. This is automatically configured and cannot be changed.

The architecture an agent needs depends on the region it deploys to — Daily-hosted regions run `arm64`, which is what this command produces. To build for a different architecture, build and push the image yourself rather than through this command.

## Error Handling

Expand Down
2 changes: 1 addition & 1 deletion pipecat-cloud/fundamentals/agent-images.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -218,7 +218,7 @@ We recommend using FastAPI to create this route. Please refer to the base image
to your own container registry.
</Note>

Pipecat Cloud requires all images to be built to target Linux on ARM. This is the most common platform for cloud deployments.
An agent image has to be built for the architecture its region runs. Daily-hosted regions run Linux on ARM, so build for `linux/arm64`:

```bash
docker build --platform linux/arm64 -t my-agent:latest .
Expand Down
4 changes: 3 additions & 1 deletion pipecat-cloud/fundamentals/error-codes.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -48,7 +48,9 @@ Check that your image repository is not rate limiting your pull requests. This c

> Image platform is not supported.

Ensure the image you are attempting to pull is supported by Pipecat Cloud. Currently, Pipecat Cloud only supports images for the `linux/arm64` platform.
The image's architecture has to match what the target region supports. Daily-hosted regions run `linux/arm64`, so an image built for `amd64` is rejected there.

Check what you built with `docker image inspect <image> --format '{{.Architecture}}'`, and rebuild with `--platform linux/arm64` if it doesn't match.

### PCC_IMAGE_PULL_UNKNOWN_ERROR

Expand Down
4 changes: 2 additions & 2 deletions pipecat-cloud/guides/ci-with-github-actions.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -157,8 +157,8 @@ If you host images in your own container registry (e.g. Docker Hub, AWS ECR, GHC

<Note>
When deploying a pre-built image, you must provide an `image-credentials`
reference if the image is in a private registry. Pipecat Cloud requires images
built for `linux/arm64`.
reference if the image is in a private registry. Build for the architecture
your region runs — `linux/arm64` for Daily-hosted regions.
</Note>

## Using v1 with Docker Build
Expand Down
Loading