Obtaining DataHub Images from Cloudsmith and ECR Instead of Docker Hub – DataHub Customer Support Portal

Area: Deployment Issues

Sub-Area: Image Registry Migration & Access

Issue

On-premise DataHub operators who previously pulled container images from Docker Hub (e.g., the acrylio/ namespace) may find that newer image versions — particularly those associated with DataHub v1.0.0 and later — are no longer published to Docker Hub. DataHub now distributes its enterprise container images primarily through Cloudsmith and AWS ECR. This affects operators who rely on automated pipelines to pull images, and who need to understand both how to obtain credentials for the new registries and which images are required for their target version. Additionally, the set of required images and their names changed in v1.0.0, with several setup and auxiliary images being deprecated or renamed.

Error Messages

Error response from daemon: manifest unknown: object not found
docker pull acrylio/acryl-api-gateway:<version> returns "object not found" for versions newer than those published to Docker Hub

You Might Be Asking

Why can't I pull the latest acryl-api-gateway image from Docker Hub?
Where are DataHub enterprise images hosted now?
How do I get credentials to access the Cloudsmith or ECR registry?
Which images do I need for DataHub v1.0.0 and later?
Are the setup images (elasticsearch-setup, postgres-setup) still required in v1.0.0+?
Is the datahub-actions image still required in v1.0.0+?

Solution

Request Cloudsmith credentials from DataHub Support.
Contact DataHub Support to obtain credentials for the Cloudsmith registry. Credentials are provided per deployment and are intended for CLI-based image pulls only — they do not provide browser-based registry UI access.
Log in to the Cloudsmith registry via Docker CLI.
Once you have received your credentials, authenticate using the following command:
```
docker login docker.datahub.com --username enterprise
Password: <your-cloudsmith-token>
```
A successful login will return Login Succeeded.
Pull images from the new registry path.
All enterprise images are now available under the docker.datahub.com/enterprise/ namespace. Replace the old acrylio/<image-name> references in your automation with the following pattern:
```
docker pull docker.datahub.com/enterprise/<image-name>:<version-tag>
```
Example:
```
docker pull docker.datahub.com/enterprise/acryl-api-gateway:v0.7.3
```

Understand which images are required for your version.

For DataHub versions prior to v1.0.0 (e.g., v0.3.x), the full image list includes setup images and the integrations service as separate components. Example pull commands for a v0.3.x-acryl release:

docker pull docker.datahub.com/enterprise/datahub-gms:<version>-acryl
docker pull docker.datahub.com/enterprise/datahub-frontend-react:<version>-acryl
docker pull docker.datahub.com/enterprise/datahub-mae-consumer:<version>-acryl
docker pull docker.datahub.com/enterprise/datahub-mce-consumer:<version>-acryl
docker pull docker.datahub.com/enterprise/datahub-upgrade:<version>-acryl
docker pull docker.datahub.com/enterprise/datahub-integrations-service:<version>-acryl
docker pull docker.datahub.com/enterprise/datahub-executor:<version>-acryl
docker pull docker.datahub.com/enterprise/datahub-mysql-setup:<version>-acryl
docker pull docker.datahub.com/enterprise/datahub-elasticsearch-setup:<version>-acryl
docker pull docker.datahub.com/enterprise/datahub-postgres-setup:<version>-acryl
docker pull docker.datahub.com/enterprise/acryl-api-gateway:<gateway-version>

For DataHub v1.0.0 and later, the required image set is simplified. The following images are available and required:

docker pull docker.datahub.com/enterprise/acryl-api-gateway:<version>
docker pull docker.datahub.com/enterprise/datahub-executor:<version>
docker pull docker.datahub.com/enterprise/datahub-executor-slim:<version>
docker pull docker.datahub.com/enterprise/datahub-frontend-react:<version>
docker pull docker.datahub.com/enterprise/datahub-gms:<version>
docker pull docker.datahub.com/enterprise/datahub-integrations-service:<version>
docker pull docker.datahub.com/enterprise/datahub-mae-consumer:<version>
docker pull docker.datahub.com/enterprise/datahub-mce-consumer:<version>
docker pull docker.datahub.com/enterprise/datahub-upgrade:<version>

Note deprecated and renamed images in v1.0.0+.
- The separate setup images (elasticsearch-setup, postgres-setup, mysql-setup) are no longer required in v1.0.0+. Upgrades now run through a consolidated system-update path. Enable global.datahub.systemUpdate.consolidatedUpgrade in your Helm values.
- The datahub-actions image is deprecated as of v1.0.0. Its functionality has been absorbed into the datahub-executor and datahub-integrations-service images. You do not need to pull or run a separate actions pod.
- Some images were renamed (not removed) when moving to the new registry:
  - acryl-elasticsearch-setup → datahub-elasticsearch-setup
  - acryl-postgres-setup → datahub-postgres-setup
Update your automation to use the new registry and image names.
Replace all references to acrylio/<image-name> in your CI/CD pipelines, Helm values, Kubernetes manifests, or infrastructure-as-code tooling with docker.datahub.com/enterprise/<image-name>. Ensure your Cloudsmith token is available as a secret in your automation environment and that the docker login step runs before any image pull steps.

Additional Notes

DataHub recommends upgrading to at least v1.0.3 when moving to the v1.0.x line, as it includes critical fixes not present in v1.0.0 or v1.0.1. The Cloudsmith token provided by DataHub Support is scoped for CLI pull operations only and cannot be used to browse the registry via a web browser. If your environment cannot use a service principal for direct ECR authentication, Cloudsmith is the recommended alternative. Docker Hub availability of enterprise images (the acrylio/ namespace) is not guaranteed for new releases; all on-premise operators should migrate their image source to the Cloudsmith registry. If you believe your release notes reference the datahub-actions image as required for v1.0.0, note that this was a documentation error — the actions pod is not needed and those release notes have been corrected.

Issue

Error Messages

You Might Be Asking

Solution

Additional Notes

Related Documentation