Set up Docker Hub and DHI upstreams with Cloudsmith-managed authentication

Cloudsmith now handles authentication for Docker Hub and Docker Hardened Images (DHI) upstreams using a managed token, removing the need to supply your own credentials during setup. Authenticated requests receive a higher rate limit than anonymous access.

How it works

When a Docker Hub or DHI upstream is created without credentials, Cloudsmith uses a managed Docker Hub organization access token (OAT) to authenticate requests on your behalf. Workspace names are shared with Docker to attribute usage when the Cloudsmith-managed token is used.

New pre-configured DHI upstream

A pre-configured DHI upstream is also available, so you can start proxying and caching images from the DHI Community tier immediately.

DHI are minimal, secure, and production-ready container base and application images maintained by Docker. Designed to reduce vulnerabilities and simplify compliance, DHI integrate easily into your existing Docker-based workflows with little to no retooling required.

To access the DHI Select or Enterprise tiers, you must configure the DHI registry as a private upstream with your Docker Hub credentials.

For more information about creating Docker Hub and DHI upstreams in Cloudsmith, see:

Keep up to date with our monthly product bulletin