This page covers running your own image, what the image must provide, and how the start command, environment variables and secrets reach it.
On the deploy page, Set overrides takes the image reference, for example ghcr.io/acme/trainer:1.4, and the registry credential to pull it with.
featherless-cloud instance create --name trainer --image ghcr.io/acme/trainer:1.4 --gpu-count 1
featherless-cloud exec --image ghcr.io/acme/trainer:1.4 --gpu-count 1 -- python train.py
Add --registry <name> to choose a registry credential for a private image.
linux/amd64.apt, dnf, yum, apk or zypper) that can install one. Without it, use the browser terminal.A tag can move to a new build between deploys. Deploy by digest (image@sha256:…) when every run must use the same build.
Add registry credentials for the registry first. With Automatic, the image is pulled without credentials when it's public, and otherwise with a credential for its registry that your organization has added.
The Start command replaces the image's default command. It's split on spaces and runs without a shell, so quotes and variables like $HOME are passed as written. To use shell features, put them in a script and run the script.
Environment variables are passed to the container and shown on the instance's Details tab. Values you set override a template's values with the same name.
Each secret is a read-only file in the container, not an environment variable:
/run/featherless/secrets/<NAME>
FEATHERLESS_SECRETS_PATH holds the folder's path. Read a secret where you need it:
export HF_TOKEN="$(cat "$FEATHERLESS_SECRETS_PATH/HF_TOKEN")"
Secrets can't be changed after an instance is deployed.