metaflow-prebuilt
A Metaflow extension that pre-bakes conda/PyPI dependencies into Docker images at deploy time. Tasks start immediately — no conda bootstrap overhead at runtime.
How it works
When you deploy a flow with --environment=prebuilt, the extension:
- Resolves the conda/PyPI environment spec for each step.
- Builds a Docker image with the environment already installed.
- Pushes the image to a registry.
- Configures the remote runner (Batch, Kubernetes, etc.) to pull that image instead of bootstrapping conda at task start.
Install
pip install metaflow-prebuilt
Optional extras for specific backends:
pip install 'metaflow-prebuilt[ecr]' # ECR registry + CodeBuild service
pip install 'metaflow-prebuilt[gcr]' # GCR registry
pip install 'metaflow-prebuilt[kaniko]' # Kaniko build service (K8s)
Quick start
from metaflow import FlowSpec, step, conda
class MyFlow(FlowSpec):
@conda(packages={"numpy": "1.26.4"})
@step
def start(self):
import numpy
print(numpy.__version__)
self.next(self.end)
@step
def end(self):
pass
if __name__ == "__main__":
MyFlow()
Deploy with the prebuilt environment (requires a configured registry and build service — see below):
# Deploy: builds and pushes Docker images, then submits the flow
python my_flow.py --environment=prebuilt run
# Or on Batch/Kubernetes:
python my_flow.py --environment=prebuilt batch run
Configuration
Select backends via environment variables:
| Variable | Default | Purpose |
|---|---|---|
METAFLOW_PREBUILT_BUILD_SERVICE |
docker |
Which build service to use |
METAFLOW_PREBUILT_IMAGE_REGISTRY |
dockerhub |
Which image registry to use |
METAFLOW_PREBUILT_REGISTRY_CACHE |
1 |
Reuse existing immutable prebuilt image tags when available |
METAFLOW_PREBUILT_BUILD_WORKERS |
min(unique image count, 8) |
Max concurrent prebuilt image builds |
Extension points
DockerBuildService
Controls how Docker images are built and pushed. Select with
METAFLOW_PREBUILT_BUILD_SERVICE=<name>.
| Name | Class | Description |
|---|---|---|
docker |
LocalDockerBuildService |
Local Docker daemon (docker build + docker push) |
buildx |
BuildxBuildService |
Docker Buildx (docker buildx build --push), supports remote builders and cross-platform |
kaniko |
KanikoBuildService |
Kaniko in a Kubernetes Job; uploads context to GCS/S3 |
codebuild |
CodeBuildService |
AWS CodeBuild; uploads context to S3, polls for completion |
ImageRegistry
Controls where images are stored. Select with
METAFLOW_PREBUILT_IMAGE_REGISTRY=<name>.
| Name | Class | Description |
|---|---|---|
dockerhub |
DockerHubRegistry |
Docker Hub (docker.io) |
ecr |
ECRRegistry |
Amazon ECR |
gcr |
GCRRegistry |
Google Container Registry |
local |
LocalRegistry |
Local registry:2 container (dev/CI use) |
Contributing a custom backend
Custom build service
Subclass DockerBuildService and implement build_and_push:
from metaflow_extensions.prebuilt.plugins.conda.build_service import DockerBuildService
class MyBuildService(DockerBuildService):
def build_and_push(self, dockerfile, context_files, image_tag,
push_credentials, echo, target_platform=None) -> bool:
# build and push; return True on success, False on failure.
# target_platform (e.g. "linux/amd64") is the resolved step's arch for
# cross-arch builds; None => builder default. Local builders should honor
# it; remote builders with a fixed build arch may ignore it.
...
Register it in your pyproject.toml:
[project.entry-points."metaflow_prebuilt.build_services"]
mybuild = "mypackage.my_module:MyBuildService"
Then use it with METAFLOW_PREBUILT_BUILD_SERVICE=mybuild.
Custom image registry
Subclass ImageRegistry and implement image_tag, push_credentials, and
pull_config:
from metaflow_extensions.prebuilt.plugins.conda.image_registry import ImageRegistry
class MyRegistry(ImageRegistry):
def image_tag(self, env_id) -> str: ...
def push_credentials(self) -> dict: ...
def pull_config(self, pull_tag) -> dict: ...
Register it:
[project.entry-points."metaflow_prebuilt.image_registries"]
myregistry = "mypackage.my_module:MyRegistry"
Then use it with METAFLOW_PREBUILT_IMAGE_REGISTRY=myregistry.
License
Apache 2.0
Metadata
Release files for metaflow-prebuilt 0.3.5
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| metaflow_prebuilt-0.3.5.tar.gz | 46.8 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| metaflow_prebuilt-0.3.5-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details |
Total release size: 101.3 kB
Release files / metaflow_prebuilt-0.3.5.tar.gz
| Download URL | metaflow_prebuilt-0.3.5.tar.gz |
|---|---|
| Size | 46.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b0e992f06a305935520c0ef9b24604ee54fb081d96e2819bd92e1eaa53b9793e
|
|
BLAKE2b-256 checksum How to use checksums |
6d9abda7bf959faa8e50ffea753eabc7954fc288402a41d70bf4b92282dc1b7f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 29, 2026.
Transparency logRelease files / metaflow_prebuilt-0.3.5-py2.py3-none-any.whl
| Download URL | metaflow_prebuilt-0.3.5-py2.py3-none-any.whl |
|---|---|
| Size | 54.5 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
a2e39ea8d92b161c3bdcf75f2acc26d07371c7a1151b27da5f8aa94dadae0704
|
|
BLAKE2b-256 checksum How to use checksums |
30874eaaa28df3401ee253d32ca7b1f7243ed141fcefc508324bcad680ed215e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 29, 2026.
Transparency logSecurity for metaflow-prebuilt 0.3.5
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for metaflow_prebuilt-0.3.5.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 29, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.