[DevOps - CentOS 7.9] Docker Local Registry (개인 Docker Hub) 구축하기

 

 

 

 

 

🗂 목차

● [DevOps - CentOS 7.9] Docker Local Registry (개인 Docker Hub) 구축하기 
● [DevOps - CentOS 7.9] Docker Local Registry 사용법
● [DevOps - CentOS 7.9] Docker Remote Registry 사용법

 

 

 

🚀 Docker Registry 구축하기

    🔽  개요

주니하랑은 기깔나는 사람들이라는 Side Project 일원으로 우리가 개발하고, 실제 Service에 이용할 Docker Container를 보다 안전하게 관리하고 싶었어요.

Docker Hub는 Private으로 관리하기 위해서는 단 한가지 Repository 밖에 이용할 수 없었고, 우리끼리 안전하게 사용할 수 있는 Docker Hub를 찾다가 Docker Registry라는 것을 찾게 되어 구축을 해보려고 해요.

        📦 구축환경

Host PC
∙ OS 정보

uname -a

 

cat /etc/*release*

∙ Hardware 정보

CPU 상세 정보 : lscpu

System Info : dmidecode -t system

Memory Info : dmidecode -t memory

 

CPU Info : dmidecode -t processor

Virtual Machine
∙ VM Application

CentOS Virtual Machine Manager

∙ VM
  - OS 정보

 

cat /etc/*release*

  - Hardware 정보

CPU Info : lscpu

 

System Info : deidecode -t system

 

Memory Info : demidecode -t memory

CPU Info : dmidecode -t processor

Application

docker --version

 

docker-compose --version

 

 

    🔽  Docker Registry

        📦 설치

최초 Docker Image를 Pull 하여 줄 거에요.

docker pull registry:latest

최신 Version에 Docker registry를 받아 주었어요.

docker images registry

Image가 잘 받아진 걸 확인할 수 있어요.

 

docker run -it \
--name Giggal-people_Docker-Hub \
--ip {Container 할당 IP} \
-d --restart=always \
-p 5000:5000 \
-v /opt/docker/volume_mapping/registry:/var/lib/registry/docker/registry/v2 \
registry:latest

위와 같이 Docker Container를 기동해 주었어요.

Option	설     명
--name	기동할 Docker Container 이름 지정
-d	Container 기동 Back Ground로 실행
-p	Host PC와 Port Mapping (Host Port : Container Port)
-v	Host PC와 Volume Mapping (Host PC Volume Path : Container Volume Path)
--restart=always	Host PC가 재부팅 되면 자동으로 해당 Container 기동
--ip	고정 IP 할당

반응형

💡 참고 사항
∙ Docker Registry Volume 관리
Docker Container로 Registry를 구축할 경우 Registry Container가 Down 된다면 Container의 정보는 휘발성이기 때문에 설정한 모든 내용이 사라진다.
이를 방어하기 위해 Volume Mapping 전략을 사용하여 Container 설정 정보가 Host PC에 남게 설정해 준다. 이렇게 하면 Container 재 기동시 자동으로 해당 정보를 가져가게 된다.

 

docker container ls

registry Docker가 기동 중인걸 확인할 수 있어요.

 

 

 

    🔽  Docker Registry Dashboard

        📦 Web Service 구축 

이번에는 우리 크루들이 보다 편리하게 Container들을 관리할 수 있도록 Web Service에서 내용들을 확인할 수 있도록 구축해 볼게요.

최초 Docker-Registry-Web을 설치하기 위해 yml File을 작성해 주어야 해요.

docker exec -it {Container ID} /bin/sh

yml을 설정하기 위해 Docker Registry의 IP를 설정하는 부분이 있어요.

이 부분은 Docker 내부 Network망과 연결을 해 주기 위해 해당 IP를 찾고자 Container에 접속을 해 주었어요.

docker exec -it {Container ID} /bin/bash

참고로 Bash Shell로 접속하기 위해 위와 같이 명령어를 입력해 주니 Bash Shell을 사용할 수 없다고 해요.
그래서 위와 같이 Shell을 사용하도록 명령어를 고쳐 주어 접속해 주었어요.

ifconfig

Container 내부 IP가 위와 같이 설정 되 있는 걸 확인하였어요.

 

docker_registry_config.yml

주니하랑은 Docker Host PC에서 위와 같이 yml File을 입력해 주었어요.

Docker Image 내려 받기 및 실행

 

docker run -it \
--ip 172.17.0.5 \
-d --restart=always \
-p 8081:8080 \
--name Giggal-people_DockerHub \
--link Giggal-people_Docker-Hub \
-v /opt/docker/config/docker_registry_config.yml:/conf/config.yml:ro \
hyper/docker-registry-web

docker container ls

Container가 정상적으로 기동 중인걸 확인할 수 있어요.

CATALINA_OPTS: -Djava.security.egd=file:/dev/./urandom -Dcontext.path=
Using CATALINA_BASE:   /var/lib/tomcat7
Using CATALINA_HOME:   /usr/share/tomcat7
Using CATALINA_TMPDIR: /var/lib/tomcat7/temp
Using JRE_HOME:        /usr/lib/jvm/java-7-openjdk-amd64
Using CLASSPATH:       /usr/share/tomcat7/bin/bootstrap.jar:/usr/share/tomcat7/bin/tomcat-juli.jar
Nov 16, 2022 1:56:23 PM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["http-bio-8080"]
Nov 16, 2022 1:56:23 PM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 2288 ms
Nov 16, 2022 1:56:23 PM org.apache.catalina.core.StandardService startInternal
INFO: Starting service Catalina
Nov 16, 2022 1:56:23 PM org.apache.catalina.core.StandardEngine startInternal
INFO: Starting Servlet Engine: Apache Tomcat/7.0.52 (Ubuntu)
2022-11-16 13:57:22,570 [localhost-startStop-1] INFO  hibernate4.HibernatePluginSupport  - Set db generation strategy to 'update' for datasource DEFAULT

Configuring Spring Security Core ...
... finished configuring Spring Security Core

2022-11-16 13:57:27,425 [localhost-startStop-1] INFO  cache.CacheBeanPostProcessor  - postProcessBeanDefinitionRegistry start
2022-11-16 13:57:27,471 [localhost-startStop-1] INFO  cache.CacheBeanPostProcessor  - postProcessBeanFactory
2022-11-16 13:57:31,840 [localhost-startStop-1] WARN  config.ConfigurationFactory  - No configuration found. Configuring ehcache from ehcache-failsafe.xml  found in the classpath: jar:file:/var/lib/tomcat7/webapps/ROOT/WEB-INF/lib/ehcache-2.9.0.jar!/ehcache-failsafe.xml
2022-11-16 13:57:36,014 [localhost-startStop-1] INFO  sql.DatabaseMetaData  - HHH000262: Table not found: access_control
2022-11-16 13:57:36,022 [localhost-startStop-1] INFO  sql.DatabaseMetaData  - HHH000262: Table not found: event
2022-11-16 13:57:36,027 [localhost-startStop-1] INFO  sql.DatabaseMetaData  - HHH000262: Table not found: role
2022-11-16 13:57:36,034 [localhost-startStop-1] INFO  sql.DatabaseMetaData  - HHH000262: Table not found: role_access
2022-11-16 13:57:36,039 [localhost-startStop-1] INFO  sql.DatabaseMetaData  - HHH000262: Table not found: user
2022-11-16 13:57:36,045 [localhost-startStop-1] INFO  sql.DatabaseMetaData  - HHH000262: Table not found: user_role
2022-11-16 13:57:36,049 [localhost-startStop-1] INFO  sql.DatabaseMetaData  - HHH000262: Table not found: access_control
2022-11-16 13:57:36,053 [localhost-startStop-1] INFO  sql.DatabaseMetaData  - HHH000262: Table not found: event
2022-11-16 13:57:36,057 [localhost-startStop-1] INFO  sql.DatabaseMetaData  - HHH000262: Table not found: role
2022-11-16 13:57:36,062 [localhost-startStop-1] INFO  sql.DatabaseMetaData  - HHH000262: Table not found: role_access
2022-11-16 13:57:36,067 [localhost-startStop-1] INFO  sql.DatabaseMetaData  - HHH000262: Table not found: user
2022-11-16 13:57:36,072 [localhost-startStop-1] INFO  sql.DatabaseMetaData  - HHH000262: Table not found: user_role
2022-11-16 13:57:36,076 [localhost-startStop-1] INFO  sql.DatabaseMetaData  - HHH000262: Table not found: access_control
2022-11-16 13:57:36,081 [localhost-startStop-1] INFO  sql.DatabaseMetaData  - HHH000262: Table not found: event
2022-11-16 13:57:36,084 [localhost-startStop-1] INFO  sql.DatabaseMetaData  - HHH000262: Table not found: role
2022-11-16 13:57:36,089 [localhost-startStop-1] INFO  sql.DatabaseMetaData  - HHH000262: Table not found: role_access
2022-11-16 13:57:36,094 [localhost-startStop-1] INFO  sql.DatabaseMetaData  - HHH000262: Table not found: user
2022-11-16 13:57:36,098 [localhost-startStop-1] INFO  sql.DatabaseMetaData  - HHH000262: Table not found: user_role
2022-11-16 13:57:37,205 [localhost-startStop-1] INFO  ehcache.GrailsEhCacheManagerFactoryBean  - Initializing EHCache CacheManager
2022-11-16 13:57:48,440 [localhost-startStop-1] WARN  web.TokenService  - Authorization disabled
2022-11-16 13:57:58,405 [localhost-startStop-1] INFO  filter.AnnotationSizeOfFilter  - Using regular expression provided through VM argument net.sf.ehcache.pool.sizeof.ignore.pattern for IgnoreSizeOf annotation : ^.*cache\..*IgnoreSizeOf$
2022-11-16 13:57:58,429 [localhost-startStop-1] INFO  sizeof.AgentLoader  - Located valid 'tools.jar' at '/usr/lib/jvm/java-7-openjdk-amd64/jre/../lib/tools.jar'
2022-11-16 13:57:58,479 [localhost-startStop-1] INFO  sizeof.JvmInformation  - Detected JVM data model settings of: 64-Bit OpenJDK JVM with Compressed OOPs
2022-11-16 13:57:58,839 [localhost-startStop-1] INFO  sizeof.AgentLoader  - Extracted agent jar to temporary file /var/lib/tomcat7/temp/ehcache-sizeof-agent4146765445260277451.jar
2022-11-16 13:57:58,839 [localhost-startStop-1] INFO  sizeof.AgentLoader  - Trying to load agent @ /var/lib/tomcat7/temp/ehcache-sizeof-agent4146765445260277451.jar
2022-11-16 13:57:58,867 [localhost-startStop-1] INFO  impl.DefaultSizeOfEngine  - using Agent sizeof engine
2022-11-16 13:57:59,046 [localhost-startStop-1] INFO  impl.DefaultSizeOfEngine  - using Agent sizeof engine
2022-11-16 13:57:59,227 [localhost-startStop-1] INFO  context.GrailsConfigUtils  - [GrailsContextLoader] Grails application loaded.
2022-11-16 13:57:59,498 [localhost-startStop-1] INFO  conf.BootStrap  - Starting registry-web ver. 0.1.3-SNAPSHOT-bededf47611365f0a6d2bb87942e3b86c1e92d9f
2022-11-16 13:57:59,702 [localhost-startStop-1] INFO  web.ConfigService  - [environmentProperties, localProperties]
2022-11-16 13:57:59,742 [localhost-startStop-1] INFO  web.ConfigService  - resolved config:
2022-11-16 13:57:59,757 [localhost-startStop-1] INFO  web.ConfigService  - registry.url: http://172.17.0.2:5000/v2
2022-11-16 13:57:59,758 [localhost-startStop-1] INFO  web.ConfigService  - registry.auth: 
2022-11-16 13:57:59,758 [localhost-startStop-1] INFO  web.ConfigService  - registry.auth.key: /config/auth.key
2022-11-16 13:57:59,758 [localhost-startStop-1] INFO  web.ConfigService  - registry.readonly: false
2022-11-16 13:57:59,759 [localhost-startStop-1] INFO  web.ConfigService  - registry.trust_any_ssl: false
2022-11-16 13:57:59,759 [localhost-startStop-1] INFO  web.ConfigService  - registry.basic_auth: 
2022-11-16 13:57:59,759 [localhost-startStop-1] INFO  web.ConfigService  - registry.enabled: false
2022-11-16 13:57:59,759 [localhost-startStop-1] INFO  web.ConfigService  - registry.auth.enabled: false
2022-11-16 13:57:59,759 [localhost-startStop-1] INFO  web.ConfigService  - registry.context_path: 
2022-11-16 13:57:59,760 [localhost-startStop-1] INFO  web.ConfigService  - registry.auth.issuer: test-issuer
2022-11-16 13:57:59,760 [localhost-startStop-1] INFO  web.ConfigService  - registry.name: 172.17.0.2:5000
2022-11-16 13:57:59,769 [localhost-startStop-1] INFO  conf.BootStrap  - auth enabled: false
Nov 16, 2022 1:58:02 PM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["http-bio-8080"]
Nov 16, 2022 1:58:02 PM org.apache.catalina.startup.Catalina start
INFO: Server startup in 98505 ms

docker logs {Container ID}

해당 Container가 잘 기동 되었는지 확인하기 위해 Log를 보니 잘 작동한 것으로 확인을 했어요.

UI가 엄청 이쁘지는 않지만, 잘 접속된걸 확인할 수 있어요.

 

 

 

🧐 참고 자료

Docker Local Registry 구축