Private registry of container images, compatible with the standard Docker and OCI protocols.
Version:
3.0.0
back to Marketplace
# Tag a local image pointing to the registry
docker tag <imagen>:<tag> <IP_DE_LA_VM>/<imagen>:<tag>
# Upload image
docker push <IP_DE_LA_VM>/<imagen>:<tag>
docker pull <IP_DE_LA_VM>/<imagen>:<tag>
docker tag mi-app:latest 200.25.101.125/mi-app:latest
docker push 200.25.101.125/mi-app:latest
docker pull 200.25.101.125/mi-app:latest
⚠️ HTTP Registry (insecure): By default, the registry runs over HTTP. Docker requires configuring the IP address as insecure-registry on the client to operate without TLS.
Add your VM's IP address to /etc/docker/daemon.json on the machine that will be doing the push/pull:
{
"insecure-registries": ["<IP_DE_LA_VM>"]
}
Then restart Docker:
sudo systemctl restart docker
# View the registry pod
kubectl get pods -A | grep docker-registry
# View the image catalog via API
curl http://<IP_DE_LA_VM>/v2/_catalog
# View installation log
tail -f /var/log/cuemby/bootstrap.log
Expected response from the catalog:
{"repositories": []}
# Verify that the registry is responding
curl http://<IP_DE_LA_VM>/v2/
# List stored images
curl http://<IP_DE_LA_VM>/v2/_catalog
# View tags of a specific image
curl http://<IP_DE_LA_VM>/v2/<imagen>/tags/list
Expected response from /v2/:
{}
💡 Tip: You can use this registry as an image source directly in k3s. Configure mirrors in /etc/rancher/k3s/registries.yaml so that the nodes resolve images from your private registry.

IaaS
Cuemby Cloud is enterprise-grade cloud infrastructure managed from a single console, built for stronger security, predictable operations, and easy scaling across regions.
Datacenters regions available in Colombia, Ecuador, and Chile
Backed by Tier III / Tier IV data center locations
Zero Network Ingress and Egress Fees
24/7 local expert support