Docker Build and Registry Push

This page covers release-oriented image naming and push behavior.

Image naming formula

<REGISTRY>/<IMAGE_PREFIX><worker-name>:<version>
<REGISTRY>/<IMAGE_PREFIX><worker-name>:latest

Example:

REGISTRY=registry.example.com
IMAGE_PREFIX=myteam/

# worker: opc-reader, version: 1.4.2
registry.example.com/myteam/opc-reader:1.4.2
registry.example.com/myteam/opc-reader:latest

Local build vs push

Local build only

npx worker-cli build opc-reader

Builds and loads image into local Docker daemon.

Push release image

npx worker-cli build opc-reader --push

Performs multi-arch push for linux/amd64,linux/arm64.

Registry-ready release checklist

1. npx worker-cli consistency
2. npx worker-cli check
3. Confirm .env has correct REGISTRY and IMAGE_PREFIX
4. npx worker-cli build <worker> --push

Large repository release example

npx worker-cli build --parallel=4 --push

[WARNING!public/PUBLISH DISCIPLINE] latest is mutable. Use explicit version tags in production deployment descriptors for deterministic rollouts.

References

• sdk/worker/repo-management/src/commands/build.ts
• sdk/worker/repo-management/src/lib/npm-proxy.ts