Docker Private Registry Now Available

docker private registry 1

We're talking about Docker today! As you may know, Docker has a tremendous amount of images on their public registry. But sometimes you may need to pull images from a private Docker registry. Mostly because you can't always publicly publish the images. So, we've added a few environement variables to allow you to fetch these images, let's see how to do it.

In this note post we assume you already have your own Docker registry. If this isn't the case, you can see how to deploy a registry server here.

So, pulling private images is done through the docker build command. To login to a private registry, you need to set a few environment variables:

  • CC_DOCKER_LOGIN_USERNAME: the username to use to login
  • CC_DOCKER_LOGIN_PASSWORD: the password of your username
  • CC_DOCKER_LOGIN_SERVER (optionnal): the server of your private registry. Defaults to Docker's public registry.

This uses the docker login command under the hood.

Build-time variables

You can use the ARG instruction to define build-time environment variables. Every environment variable defined for your application will be passed as a build environment variable using the --build-arg=<ENV> parameter during the docker build.

Source image: Vladimir Malyavko

Blog

À lire également

UP Program: Clever Cloud announces its fifth startup selection

With this new batch, Clever Cloud welcomes four startups to the UP Program: Sentibee, Pictaderm, Legaia and Cockpit Agriculture.
Company

Sōzu 2.0 — turning a reverse proxy into a programmable edge

Sōzu is the reverse proxy that sits in front of every application running on Clever Cloud. After eighteen months of work — first the HTTP/2 multiplexer, built on our existing kawa pivot, then almost every other layer of the proxy, and finally a long run in production on the cleverapps.io load balancers — Sōzu 2.0 is out.
Engineering

K3s vs K8s: What Are the Differences and Which One Should You Choose in 2026?

Kubernetes has become the standard for container orchestration. But depending on your infrastructure constraints (limited resources, edge computing, IoT, or large-scale enterprise clusters), the distribution you choose can radically change the operational experience. K3s and K8s (upstream Kubernetes) address different needs, even though both share the same CNCF-certified foundation.
Engineering Features