Host your own docker registry | Local Docker Registry | Docker Registry using Docker Compose

Host your own docker registry | Local Docker Registry | Docker Registry using Docker Compose


shared hosting docker

In this video we will learn about hosing our own docker registry. we will host docker registry and docker registry UI using docker compose. Then we will push image to that docker registry and we will pull image from docker registry.

Post Link :

Docker Image Links


version: ‘3’

services:
docker-registry:
container_name: docker-registry
image: registry:2
ports:
– 5000:5000
restart: always
volumes:
– ./volume:/var/lib/registry
docker-registry-ui:
container_name: docker-registry-ui
image: konradkleine/docker-registry-frontend:v2
ports:
– 8080:80
environment:
ENV_DOCKER_REGISTRY_HOST: docker-registry
ENV_DOCKER_REGISTRY_PORT: 5000

————————————————————–
{
“insecure-registries”:[“selftuts.local.com:5000”]
}

28 thoughts on “Host your own docker registry | Local Docker Registry | Docker Registry using Docker Compose

  1. Nice tutorial. However, I was trying to push the image from a system running on Windows 10. According to the docker documentation, the deamon.json file is located under the path C:/ProgramData/Docker/config/daemon.json. So I created the file but the insecure-registries changes were not applied after restarting the daemon. I found that you simply have to add your insecure registry via the docker desktop client under settings -> Docker Engine. Then the daemon.json file is explicitly shown there where changes can be applied. Maybe this helps someone else running into this issue.

  2. Hi, great tutorial, but one thing, let's say I've used docker-compose.yml to do a project, obviously the images will be build. If I push thoses images, will I get the code inside ? and reconstruct the docker-compose on another host ?

Leave a Reply

Your email address will not be published. Required fields are marked *