supabase-studio

packaged by Chainguard

Chainguard Container for supabase-studio

A minimal, wolfi-based image for Supabase Studio, the web dashboard for managing a Supabase Postgres development platform stack.

Chainguard Containers are regularly-updated, secure-by-default container images.

Download this Container Image

For those with access, this container image is available on cgr.dev:

docker pull cgr.dev/ORGANIZATION/supabase-studio:latest

Be sure to replace the ORGANIZATION placeholder with the name used for your organization's private repository within the Chainguard Registry.

Compatibility Notes

The Chainguard supabase-studio image is a replacement for the upstream supabase/studio image. It is built from the apps/studio Next.js (TypeScript) application in the supabase/supabase monorepo, which is licensed under the Apache License 2.0. Refer to the upstream releases and the Chainguard Containers Directory for the versions and tags currently available.

The image keeps the upstream launch contract: the entrypoint is the Node.js docker-entrypoint.sh script, the default command is node apps/studio/server.js, and the working directory is /app, where the Next.js standalone server tree is installed.

Unlike the upstream image, which runs as root, this image runs as the nonroot user with UID 65532 by default. The Next.js cache directory /app/apps/studio/.next/cache is writable by that user. If you mount a volume over it, make sure the mounted path is writable by UID 65532.

The upstream image also ships build tooling (pnpm, Yarn, gcc, git, Python) that the standalone server does not need at runtime. This image does not include them.

Getting Started

Studio is a dashboard for a Supabase stack. To be useful, it needs to reach postgres-meta (for database introspection) and the Supabase API gateway. The most direct way to run it is to use the upstream self-hosted Docker Compose setup and swap in this image.

Clone the repository and copy the example environment file:

git clone --depth 1 https://github.com/supabase/supabase.git
cd supabase/docker
cp .env.example .env

Before going further, follow the self-hosting guide to replace the demo secrets in .env. Then open docker-compose.yml, change the image: of the studio service to cgr.dev/ORGANIZATION/supabase-studio:latest, and start the stack:

docker compose up -d

Compose places every service on one shared network, so Studio can reach postgres-meta at http://meta:8080 and the gateway at http://kong:8000, and the dashboard is served through the gateway.

To attach Studio to a stack that is already running, find the Compose network (usually docker_default) and join it:

docker network ls

export SUPABASE_ANON_KEY='<anon-key>'
export SUPABASE_SERVICE_KEY='<service-key>'
export POSTGRES_PASSWORD='<postgres-password>'

docker run --rm -p 3000:3000 \
  --network docker_default \
  -e STUDIO_PG_META_URL='http://meta:8080' \
  -e SUPABASE_URL='http://kong:8000' \
  -e SUPABASE_ANON_KEY="$SUPABASE_ANON_KEY" \
  -e SUPABASE_SERVICE_KEY="$SUPABASE_SERVICE_KEY" \
  cgr.dev/ORGANIZATION/supabase-studio:latest

Set the two keys to the ANON_KEY and SERVICE_ROLE_KEY values from your .env file. Check that Studio is up with the health endpoint the upstream healthcheck uses:

curl http://localhost:3000/api/platform/profile

Deploying with Helm

Studio runs on Kubernetes as part of the community-maintained Supabase Helm chart. The chart installs Studio together with Postgres, postgres-meta, the Kong API gateway, and the other Supabase services. Add the chart repository:

helm repo add supabase https://supabase-community.github.io/supabase-kubernetes
helm repo update

Create a values.yaml file that points the Studio component at the Chainguard image:

cat > values.yaml <<EOF
image:
  studio:
    repository: cgr.dev/ORGANIZATION/supabase-studio
    tag: latest
EOF

Install the chart with the values file:

helm install supabase supabase/supabase \
  --namespace supabase --create-namespace \
  --values values.yaml

The chart also pulls companion images. Chainguard offers images for some of them:

• image.kong: the kong image.
• image.rest: the postgrest image.
• image.auth: the gotrue image.
• image.vector: the vector image.
• image.minio and image.minioClient: the chart's defaults already use Chainguard's minio and minio-client images.

Before you switch a companion, check that its version is compatible with the chart. Keep image.db on the upstream supabase/postgres image. It is a customized Postgres build with Supabase-specific extensions, roles, and schemas, so a generic image such as Chainguard's postgres cannot replace it directly.

If your registry requires authentication, add pull secrets with image.studio.pullSecrets. Before deploying to production, replace the chart's demo credentials under secret (JWT keys, database password, and dashboard credentials) with your own values. The chart's values.yaml lists every option.

Configuration

Studio is configured with environment variables. The example below fits the Compose network from Getting Started. It serves Studio on port 8082 instead of 3000 and adds the database password and public URL that the SQL editor and API settings pages use:

docker run --rm -p 8082:8082 \
  --network docker_default \
  -e PORT=8082 \
  -e HOSTNAME=0.0.0.0 \
  -e STUDIO_PG_META_URL='http://meta:8080' \
  -e SUPABASE_URL='http://kong:8000' \
  -e SUPABASE_PUBLIC_URL='http://localhost:8000' \
  -e SUPABASE_ANON_KEY="$SUPABASE_ANON_KEY" \
  -e SUPABASE_SERVICE_KEY="$SUPABASE_SERVICE_KEY" \
  -e POSTGRES_PASSWORD="$POSTGRES_PASSWORD" \
  cgr.dev/ORGANIZATION/supabase-studio:latest

Adapt these values to your deployment:

• PORT: The port the server listens on. The image sets it to 3000 by default. Keep the published port (-p) the same.
• HOSTNAME: The address the server binds to. 0.0.0.0 accepts connections from outside the container.
• STUDIO_PG_META_URL: The URL of the postgres-meta service on the shared network.
• SUPABASE_URL: The internal URL of the API gateway. SUPABASE_PUBLIC_URL is the URL that browsers use to reach it.
• SUPABASE_ANON_KEY and SUPABASE_SERVICE_KEY: The ANON_KEY and SERVICE_ROLE_KEY values from your .env file.
• POSTGRES_PASSWORD: The POSTGRES_PASSWORD value from your .env file.

Documentation and Resources

• Supabase GitHub Repository
• Supabase Self-Hosting Guide
• Supabase Helm Chart

What are Chainguard Containers?

Chainguard's free tier of Starter container images are built with Wolfi, our minimal Linux undistro.

All other Chainguard Containers are built with Chainguard OS, Chainguard's minimal Linux operating system designed to produce container images that meet the requirements of a more secure software supply chain.

The main features of Chainguard Containers include:

• Minimal design, without unnecessary software bloat
• Daily builds to ensure container images are up-to-date with available security patches
• High quality build-time SBOMs attesting to the provenance of all artifacts within the image
• Verifiable signatures provided by Sigstore
• Reproducible builds with Cosign and apko (read more about reproducibility)

For cases where you need container images with shells and package managers to build or debug, most Chainguard Containers come paired with a development, or -dev, variant.

In all other cases, including Chainguard Containers tagged as :latest or with a specific version number, the container images include only an open-source application and its runtime dependencies. These minimal container images typically do not contain a shell or package manager.

Although the -dev container image variants have similar security features as their more minimal versions, they include additional software that is typically not necessary in production environments. We recommend using multi-stage builds to copy artifacts from the -dev variant into a more minimal production image.

Need additional packages?

To improve security, Chainguard Containers include only essential dependencies. Need more packages? Chainguard customers can use Custom Assembly to add packages, either through the Console, chainctl, or API.

To use Custom Assembly in the Chainguard Console: navigate to the image you'd like to customize in your Organization's list of images, and click on the Customize image button at the top of the page.

Learn More

Refer to our Chainguard Containers documentation on Chainguard Academy. Chainguard also offers VMs and Libraries — contact us for access.

Trademarks

This software listing is packaged by Chainguard. The trademarks set forth in this offering are owned by their respective companies, and use of them does not imply any affiliation, sponsorship, or endorsement by such companies.