$ aws s3 cp s3://aipin-bucket/CentOS-7-x86_64-Everything-2009.iso /root download: s3://aipin-bucket/CentOS-7-x86_64-Everything-2009.iso to ./CentOS-7-x86_64-Everything-2009.iso $ cd /etc/yum.repos.d $ ll $ mkdir backup $ mv *.repo backup/ $ cd backup $ ll $ vi local_repository
1 2 3 4 5
[Cento OS7 Repository] name=CentOS Local Repository baseurl=file:///root/local_repo/CentOS-7/ gpgcheck=0 enabled=1
1 2 3 4 5 6 7 8 9 10 11
$ yum clean all Loaded plugins: extras_suggestions, langpacks, priorities, update-motd There are no enabled repos. Run "yum repolist all" to see the repos you have. To enable Red Hat Subscription Management repositories: subscription-manager repos --enable <repo> To enable custom repositories: yum-config-manager --enable <repo> $ yum repolist Loaded plugins: extras_suggestions, langpacks, priorities, update-motd repolist: 0
$ rpm -ivh createrepo_c-0.12.2-2.amzn2.0.2.x86_64.rpm error: Failed dependencies: createrepo_c-libs = 0.12.2-2.amzn2.0.2 is needed by createrepo_c-0.12.2-2.amzn2.0.2.x86_64 libcreaterepo_c.so.0()(64bit) is needed by createrepo_c-0.12.2-2.amzn2.0.2.x86_64
의존성 문제를 해결하기 위해 필요한 패키지를 함께 설치해야 합니다. 이 경우에는 createrepo_c-libs와 libcreaterepo_c.so.0 라이브러리를 포함하는 패키지를 함께 설치해야 합니다.
One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=<repoid> ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage:
yum-config-manager --disable <repoid> or subscription-manager repos --disable=<repoid>
5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise:
Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again Installation failed. Check that you have permissions to install.
현재 문제는 epel 리포지토리가 활성화되어 있지만 해당 리포지토리에 접근할 수 없어서 발생하는 것이다.
일시적으로 epel 리보지토리를 비활성화하고 진행하곘다.
1
$ sudo yum --disablerepo=epel install docker
잘 설치되었다.
2. Docker 서비스 시작 및 자동 시작 설정
Docker가 설치된 후, Docker 데몬을 시작하고 시스템 부팅 시 자동으로 시작되도록 설정해야 한다.
