Inviare l'immagine a un registry

The cloud cannot pull an image off your laptop. You first push it to a container registry, a shared place that runtimes can pull from. 🚀

Each cloud has its own: AWS uses ECR, Google uses Artifact Registry, and Docker Hub works everywhere. Pick the one near your runtime.

A full image name encodes its registry host, repository, and tag. The runtime reads that address to know exactly where to pull from.

Use docker tag to give your local image its full registry name. The push command uses this name to find the destination.

Registries are private by default. Run docker login with your credentials so the daemon is allowed to push and pull images.

Now docker push uploads each layer to the registry. Shared base layers are skipped, so only your new code travels over the wire.

The latest tag is a moving target, so two pulls can give different images. Always deploy a specific, immutable version tag.

A great trick is tagging images with the git commit SHA. Then any running container traces straight back to the exact source code.

Tags can be overwritten, but a digest is a content hash that never moves. Pin production deploys to a digest for full certainty.

From a clean machine, run docker pull on the full name. If it downloads cleanly, the cloud runtime will be able to pull it too.

Once the image is pushed and tagged, the registry becomes the single source the cloud deploys from. Your handoff to production is done.

Let us check what makes a deploy reproducible.

You tagged the image, logged in, and pushed it to a registry with an immutable version. The cloud can now pull your model anywhere. 🐳