metaflow-metadata-service

Chainguard Container for metaflow-metadata-service

A minimal, wolfi-based image for Metaflow Metadata Service. Metaflow Metadata Service is a backend service for tracking and managing ML workflow metadata.

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/metaflow-metadata-service: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 metaflow-metadata-service image is designed as a drop-in replacement for the upstream netflixoss/metaflow_metadata_service image.

Key differences from the upstream image:

• Virtual environment located at /usr/share/metaflow-service/venv
• Services directory at /usr/share/metaflow-service/services
• The goose database migration tool is included

Getting Started

Prerequisites

Metaflow Metadata Service requires a PostgreSQL database. Set up your database and note the connection details.

Docker

Run the metadata service with environment variables for database configuration:

docker run -d --name metaflow-metadata \
  -p 8080:8080 \
  -e MF_METADATA_DB_HOST='your-postgres-host' \
  -e MF_METADATA_DB_PORT=5432 \
  -e MF_METADATA_DB_USER='postgres' \
  -e MF_METADATA_DB_PSWD='your-password' \
  -e MF_METADATA_DB_NAME='metaflow' \
  cgr.dev/ORGANIZATION/metaflow-metadata-service:latest

Verify the service is running:

curl http://localhost:8080/ping
# Expected response: pong

Database Migrations

Run database migrations using the included goose tool:

docker run --rm \
  -e MF_METADATA_DB_HOST='your-postgres-host' \
  -e MF_METADATA_DB_PORT=5432 \
  -e MF_METADATA_DB_USER='postgres' \
  -e MF_METADATA_DB_PSWD='your-password' \
  -e MF_METADATA_DB_NAME='metaflow' \
  --entrypoint /usr/share/metaflow-service/venv/bin/python3 \
  cgr.dev/ORGANIZATION/metaflow-metadata-service:latest \
  /usr/share/metaflow-service/run_goose.py --upgrade

Running Different Services

The image includes three services:

Metadata Service (default, port 8080):

docker run -p 8080:8080 cgr.dev/ORGANIZATION/metaflow-metadata-service:latest

Migration Service (port 8082):

docker run -p 8082:8082 \
  --entrypoint /usr/share/metaflow-service/venv/bin/migration_service \
  cgr.dev/ORGANIZATION/metaflow-metadata-service:latest

UI Backend Service (port 8083):

docker run -p 8083:8083 \
  --entrypoint /usr/share/metaflow-service/venv/bin/ui_backend_service \
  cgr.dev/ORGANIZATION/metaflow-metadata-service:latest

Configuration

Environment Variables

Configuring Metaflow Client

Point your Metaflow client to use this service:

export METAFLOW_SERVICE_URL=http://localhost:8080
export METAFLOW_DEFAULT_METADATA=service
python3 your_flow.py run

Or configure via ~/.metaflowconfig/config.json:

{
  "METAFLOW_SERVICE_URL": "http://your-service-host:8080",
  "METAFLOW_DEFAULT_METADATA": "service"
}

Documentation and Resources

• Metaflow Service GitHub
• Metaflow Documentation
• Metaflow GitHub
• Configuring Metaflow

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.