Skip to content

Docker Registry

wodby ci init requests registry credentials for the current build and logs Docker in to the registry associated with your application.

wodby ci release [SERVICE]... pushes the images built during wodby ci build. If you do not specify services, the CLI releases all built services from the current build.

By default, Wodby uses Wodby Registry, but you can also attach another registry integration such as Docker Hub or Distribution Registry.

Built images are tagged as:

[registry-host]/[registry-repository]:[service]-[build-number]

For Docker Hub registry integrations, the registry host is docker.io. The registry repository is based on the Docker Hub namespace and app instance name, for example:

[namespace]/[app-name]_[app-instance-name]-[suffix]

Docker Hub push operations use the integration's main credentials. Deployment image pulls use the optional pull-only credentials when both pull-only fields are set; otherwise they use the main credentials.

For Distribution Registry integrations, the registry host is the normalized integration host without http:// or https://. The registry repository is based on the optional repository prefix and app instance name, for example:

[prefix]/[app-name]_[app-instance-name]-[suffix]

If the integration does not define a repository prefix, Wodby uses the organization machine name. Distribution Registry push operations use the integration's main credentials. Deployment image pulls use the optional pull-only credentials when both pull-only fields are set; otherwise they use the main credentials.

wodby ci release can also publish additional tags:

  • --branch-tag pushes a tag based on the current git branch
  • --latest-branch <branch> updates the latest tag when the build comes from the selected branch