Migrate Jitterbit App Builder Docker images from the private registry to Docker Hub
Introduction
Jitterbit has historically published App Builder and Vinyl Docker images to a private Docker registry, registry.zudy.com. These images are also published to the public Docker Hub registry.
Important
The private Docker registry (registry.zudy.com) is scheduled to be decommissioned on February 24, 2027. Jitterbit will continue to publish new App Builder and Vinyl Docker images to it until that date. If your deployment pulls images from this registry, migrate to the public Docker Hub registry now. After the registry is decommissioned, deployments still pointing to it will stop receiving updates, and may experience downtime if the hosting provider has not already cached the image.
Migrating requires no App Builder configuration changes. You only need to update the image name or URL your deployment references, as described below. The image tag, image contents, and App Builder behavior stay the same.
Map a private registry image name to its Docker Hub equivalent
A private registry image name is composed of four parts. For example:
registry.zudy.com/vinyl/release:4.67
| Part | Example value | Description |
|---|---|---|
| Registry host name | registry.zudy.com |
The private registry's host name. |
| Namespace | vinyl |
An organization or project name. |
| Repository | release |
The repository name. |
| Image tag | 4.67 |
The image's version tag. |
The equivalent Docker Hub image name for App Builder 4.x is:
jitterbit/app-builder:4.67
(The full form of this name is docker.io/jitterbit/app-builder:4.67, but the docker.io host name is commonly omitted since it's the default registry Docker uses.) The namespace changes to the jitterbit organization, and the repository changes to app-builder. The image tag keeps the same name and meaning.
For older, 3.x versions of Vinyl, use the jitterbit/vinyl repository instead. For example, registry.zudy.com/vinyl/release:3.3.38705 on the private registry is jitterbit/vinyl:3.3.38705 on Docker Hub.
See Supported tags for the full list of tag formats Jitterbit publishes.
Private registry to Docker Hub image name reference
Refer to the following table for additional examples:
| Private registry image name | Docker Hub image name |
|---|---|
registry.zudy.com/vinyl/release:latest |
jitterbit/app-builder:latest |
registry.zudy.com/vinyl/release:4 |
jitterbit/app-builder:4 |
registry.zudy.com/vinyl/release:4.67 |
jitterbit/app-builder:4.67 |
registry.zudy.com/vinyl/release:4.67.0.39401 |
jitterbit/app-builder:4.67.0.39401 |
registry.zudy.com/vinyl/release:3.3 |
jitterbit/vinyl:3.3 |
registry.zudy.com/vinyl/release:3.3.38705 |
jitterbit/vinyl:3.3.38705 |
As long as the image tag stays the same, switching from a private registry image name to its Docker Hub equivalent is seamless.
Update your deployment
In your deployment, replace the private registry image name with its Docker Hub equivalent. The images on Docker Hub are public, so pulling them does not require credentials, and you no longer need the credentials your deployment uses for the private registry.
Where you change the image depends on how you deploy App Builder:
-
Docker: Change the image name in your
docker runcommand or theimagevalue in your Docker Compose file. -
Azure Container Apps: On the Container tab, set Image type to Public, Registry login server to
docker.io, and Image and tag to the Docker Hub image name. For the full setup, see the Azure Container Apps guide. -
Azure App Service: On the Container tab, set Image and Tag to the Docker Hub image name. For the full setup, see App Builder setup on Microsoft Azure.
On any other platform, change the image name in the same place you currently set it.