Docker registries
Docker registry publishing is for Fission SSR and Static site targets packaged as container images.
1. Package the image
fission package --project-dir examples/pokemon-card-store --target ssr --format docker-image --release
The package step should build or prepare the image with the tags configured in fission.toml.
2. Authenticate with the registry
Use the Docker-compatible registry authentication flow for the target registry. Fission does not store registry passwords. Use the Docker CLI session, CI secrets, environment references, or operating-system key stores.
3. Publish tags
fission publish \
--project-dir examples/pokemon-card-store \
--provider docker-registry \
--artifact target/fission/release/ssr/docker-image/artifact-manifest.json \
--site production
The receipt should record image tags, digests where available, registry host, pushed byte counts, and provider output.
After publishing, check the remote registry state with:
fission distribute status \
--project-dir examples/pokemon-card-store \
--provider docker-registry \
--site production
The status receipt inspects each configured tag. If the distribution profile does
not list tags, pass --artifact so Fission can inspect the image tags recorded
in image-metadata.json. The receipt reports the manifest digest when Docker
exposes it.
Fission
A cross-platform, GPU-accelerated user interface framework for Rust. MIT licensed.
Copyright (c) 2026 Fission
Ready to use today. Widget APIs are expected to remain stable; some runtime and shell APIs may change before 1.0.0.
Fission 0.7.0