인프런 커뮤니티 질문&답변
작성한 질문수
vagrant up 설치 할시에 에러 뜹니다.
작성
·
157
0
쿠버네틱스 강의 듣고 있는데 계속 에러가 떠서 뭐 할 수가 없네요 2일간 구글링 해봤는데 안되서 여기다가 질문 날립니다.
아래는 쿠버넷 에러나는 곳만 발췌한 부분입니다.
w3-k8s-1.25.0: Loaded plugins: fastestmirror
w3-k8s-1.25.0: Determining fastest mirrors
w3-k8s-1.25.0: * base: mirror.navercorp.com
w3-k8s-1.25.0: * extras: mirror.navercorp.com
w3-k8s-1.25.0: * updates: mirror.navercorp.com
w3-k8s-1.25.0: https://packages.cloud.google.com/yum/repos/kubernetes-el7-x86_64/repodata/repomd.xml: [Errno 14] curl#60 - "The certificate issuer's certificate has expired. Check your system date and time."
w3-k8s-1.25.0: Trying other mirror.
w3-k8s-1.25.0: It was impossible to connect to the CentOS servers.
w3-k8s-1.25.0: This could mean a connectivity issue in your environment, such as the requirement to configure a proxy,
w3-k8s-1.25.0: or a transparent proxy that tampers with TLS security, or an incorrect system clock.
w3-k8s-1.25.0: You can try to solve this issue by using the instructions on https://wiki.centos.org/yum-errors
w3-k8s-1.25.0: If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
w3-k8s-1.25.0:
w3-k8s-1.25.0:
w3-k8s-1.25.0:
w3-k8s-1.25.0: One of the configured repositories failed (Kubernetes),
w3-k8s-1.25.0: and yum doesn't have enough cached data to continue. At this point the only
w3-k8s-1.25.0: safe thing yum can do is fail. There are a few ways to work "fix" this:
w3-k8s-1.25.0:
w3-k8s-1.25.0: 1. Contact the upstream for the repository and get them to fix the problem.
w3-k8s-1.25.0:
w3-k8s-1.25.0: 2. Reconfigure the baseurl/etc. for the repository, to point to a working
w3-k8s-1.25.0: upstream. This is most often useful if you are using a newer
w3-k8s-1.25.0: distribution release than is supported by the repository (and the
w3-k8s-1.25.0: packages for the previous distribution release still work).
w3-k8s-1.25.0:
w3-k8s-1.25.0: 3. Run the command with the repository temporarily disabled
w3-k8s-1.25.0: yum --disablerepo=kubernetes ...
w3-k8s-1.25.0:
w3-k8s-1.25.0: 4. Disable the repository permanently, so yum won't use it by default. Yum
w3-k8s-1.25.0: will then just ignore the repository until you permanently enable it
w3-k8s-1.25.0: again or use --enablerepo for temporary usage:
w3-k8s-1.25.0:
w3-k8s-1.25.0: yum-config-manager --disable kubernetes
w3-k8s-1.25.0: or
w3-k8s-1.25.0: subscription-manager repos --disable=kubernetes
w3-k8s-1.25.0:
w3-k8s-1.25.0: 5. Configure the failing repository to be skipped, if it is unavailable.
w3-k8s-1.25.0: Note that yum will try to contact the repo. when it runs most commands,
w3-k8s-1.25.0: so will have to try and fail each time (and thus. yum will be be much
w3-k8s-1.25.0: slower). If it is a very temporary problem though, this is often a nice
w3-k8s-1.25.0: compromise:
w3-k8s-1.25.0:
w3-k8s-1.25.0: yum-config-manager --save --setopt=kubernetes.skip_if_unavailable=true
w3-k8s-1.25.0:
w3-k8s-1.25.0: failure: repodata/repomd.xml from kubernetes: [Errno 256] No more mirrors to try.
w3-k8s-1.25.0: https://packages.cloud.google.com/yum/repos/kubernetes-el7-x86_64/repodata/repomd.xml: [Errno 14] curl#60 - "The certificate issuer's certificate has expired. Check your system date and time."
여기서 아래는 Vagrant Up 한 이후의 전문입니다.
$ vagrant up
Bringing machine 'm-k8s-1.25.0' up with 'virtualbox' provider...
Bringing machine 'w1-k8s-1.25.0' up with 'virtualbox' provider...
Bringing machine 'w2-k8s-1.25.0' up with 'virtualbox' provider...
Bringing machine 'w3-k8s-1.25.0' up with 'virtualbox' provider...
==> m-k8s-1.25.0: Checking if box 'sysnet4admin/CentOS-k8s' version '0.7.4' is up to date...
==> m-k8s-1.25.0: Clearing any previously set forwarded ports...
==> m-k8s-1.25.0: Clearing any previously set network interfaces...
==> m-k8s-1.25.0: Preparing network interfaces based on configuration...
m-k8s-1.25.0: Adapter 1: nat
m-k8s-1.25.0: Adapter 2: hostonly
==> m-k8s-1.25.0: Forwarding ports...
m-k8s-1.25.0: 22 (guest) => 60010 (host) (adapter 1)
==> m-k8s-1.25.0: Running 'pre-boot' VM customizations...
==> m-k8s-1.25.0: Booting VM...
==> m-k8s-1.25.0: Waiting for machine to boot. This may take a few minutes...
m-k8s-1.25.0: SSH address: 127.0.0.1:60010
m-k8s-1.25.0: SSH username: vagrant
m-k8s-1.25.0: SSH auth method: private key
==> m-k8s-1.25.0: Machine booted and ready!
==> m-k8s-1.25.0: Checking for guest additions in VM...
m-k8s-1.25.0: The guest additions on this VM do not match the installed version of
m-k8s-1.25.0: VirtualBox! In most cases this is fine, but in rare cases it can
m-k8s-1.25.0: prevent things such as shared folders from working properly. If you see
m-k8s-1.25.0: shared folder errors, please make sure the guest additions within the
m-k8s-1.25.0: virtual machine match the version of VirtualBox you have installed on
m-k8s-1.25.0: your host and reload your VM.
m-k8s-1.25.0:
m-k8s-1.25.0: Guest Additions Version: 5.2.12
m-k8s-1.25.0: VirtualBox Version: 6.1
==> m-k8s-1.25.0: Setting hostname...
==> m-k8s-1.25.0: Configuring and enabling network interfaces...
==> m-k8s-1.25.0: Machine already provisioned. Run `vagrant provision` or use the `--provision`
==> m-k8s-1.25.0: flag to force provisioning. Provisioners marked to run always will still run.
==> w1-k8s-1.25.0: Checking if box 'sysnet4admin/CentOS-k8s' version '0.7.4' is up to date...
==> w1-k8s-1.25.0: Clearing any previously set forwarded ports...
==> w1-k8s-1.25.0: Clearing any previously set network interfaces...
==> w1-k8s-1.25.0: Preparing network interfaces based on configuration...
w1-k8s-1.25.0: Adapter 1: nat
w1-k8s-1.25.0: Adapter 2: hostonly
==> w1-k8s-1.25.0: Forwarding ports...
w1-k8s-1.25.0: 22 (guest) => 60101 (host) (adapter 1)
==> w1-k8s-1.25.0: Running 'pre-boot' VM customizations...
==> w1-k8s-1.25.0: Booting VM...
==> w1-k8s-1.25.0: Waiting for machine to boot. This may take a few minutes...
w1-k8s-1.25.0: SSH address: 127.0.0.1:60101
w1-k8s-1.25.0: SSH username: vagrant
w1-k8s-1.25.0: SSH auth method: private key
==> w1-k8s-1.25.0: Machine booted and ready!
==> w1-k8s-1.25.0: Checking for guest additions in VM...
w1-k8s-1.25.0: The guest additions on this VM do not match the installed version of
w1-k8s-1.25.0: VirtualBox! In most cases this is fine, but in rare cases it can
w1-k8s-1.25.0: prevent things such as shared folders from working properly. If you see
w1-k8s-1.25.0: shared folder errors, please make sure the guest additions within the
w1-k8s-1.25.0: virtual machine match the version of VirtualBox you have installed on
w1-k8s-1.25.0: your host and reload your VM.
w1-k8s-1.25.0:
w1-k8s-1.25.0: Guest Additions Version: 5.2.12
w1-k8s-1.25.0: VirtualBox Version: 6.1
==> w1-k8s-1.25.0: Setting hostname...
==> w1-k8s-1.25.0: Configuring and enabling network interfaces...
==> w1-k8s-1.25.0: Machine already provisioned. Run `vagrant provision` or use the `--provision`
==> w1-k8s-1.25.0: flag to force provisioning. Provisioners marked to run always will still run.
==> w2-k8s-1.25.0: Checking if box 'sysnet4admin/CentOS-k8s' version '0.7.4' is up to date...
==> w2-k8s-1.25.0: Clearing any previously set forwarded ports...
==> w2-k8s-1.25.0: Clearing any previously set network interfaces...
==> w2-k8s-1.25.0: Preparing network interfaces based on configuration...
w2-k8s-1.25.0: Adapter 1: nat
w2-k8s-1.25.0: Adapter 2: hostonly
==> w2-k8s-1.25.0: Forwarding ports...
w2-k8s-1.25.0: 22 (guest) => 60102 (host) (adapter 1)
==> w2-k8s-1.25.0: Running 'pre-boot' VM customizations...
==> w2-k8s-1.25.0: Booting VM...
==> w2-k8s-1.25.0: Waiting for machine to boot. This may take a few minutes...
w2-k8s-1.25.0: SSH address: 127.0.0.1:60102
w2-k8s-1.25.0: SSH username: vagrant
w2-k8s-1.25.0: SSH auth method: private key
w2-k8s-1.25.0: Warning: Connection reset. Retrying...
==> w2-k8s-1.25.0: Machine booted and ready!
==> w2-k8s-1.25.0: Checking for guest additions in VM...
w2-k8s-1.25.0: The guest additions on this VM do not match the installed version of
w2-k8s-1.25.0: VirtualBox! In most cases this is fine, but in rare cases it can
w2-k8s-1.25.0: prevent things such as shared folders from working properly. If you see
w2-k8s-1.25.0: shared folder errors, please make sure the guest additions within the
w2-k8s-1.25.0: virtual machine match the version of VirtualBox you have installed on
w2-k8s-1.25.0: your host and reload your VM.
w2-k8s-1.25.0:
w2-k8s-1.25.0: Guest Additions Version: 5.2.12
w2-k8s-1.25.0: VirtualBox Version: 6.1
==> w2-k8s-1.25.0: Setting hostname...
==> w2-k8s-1.25.0: Configuring and enabling network interfaces...
==> w2-k8s-1.25.0: Machine already provisioned. Run `vagrant provision` or use the `--provision`
==> w2-k8s-1.25.0: flag to force provisioning. Provisioners marked to run always will still run.
==> w3-k8s-1.25.0: Importing base box 'sysnet4admin/CentOS-k8s'...
==> w3-k8s-1.25.0: Matching MAC address for NAT networking...
==> w3-k8s-1.25.0: Checking if box 'sysnet4admin/CentOS-k8s' version '0.7.4' is up to date...
==> w3-k8s-1.25.0: Setting the name of the VM: w3-k8s-1.25.0(github_SysNet4Admin)
==> w3-k8s-1.25.0: Clearing any previously set network interfaces...
==> w3-k8s-1.25.0: Preparing network interfaces based on configuration...
w3-k8s-1.25.0: Adapter 1: nat
w3-k8s-1.25.0: Adapter 2: hostonly
==> w3-k8s-1.25.0: Forwarding ports...
w3-k8s-1.25.0: 22 (guest) => 60103 (host) (adapter 1)
==> w3-k8s-1.25.0: Running 'pre-boot' VM customizations...
==> w3-k8s-1.25.0: Booting VM...
==> w3-k8s-1.25.0: Waiting for machine to boot. This may take a few minutes...
w3-k8s-1.25.0: SSH address: 127.0.0.1:60103
w3-k8s-1.25.0: SSH username: vagrant
w3-k8s-1.25.0: SSH auth method: private key
w3-k8s-1.25.0: Warning: Connection reset. Retrying...
w3-k8s-1.25.0:
w3-k8s-1.25.0: Vagrant insecure key detected. Vagrant will automatically replace
w3-k8s-1.25.0: this with a newly generated keypair for better security.
w3-k8s-1.25.0:
w3-k8s-1.25.0: Inserting generated public key within guest...
w3-k8s-1.25.0: Removing insecure key from the guest if it's present...
w3-k8s-1.25.0: Key inserted! Disconnecting and reconnecting using new SSH key...
==> w3-k8s-1.25.0: Machine booted and ready!
==> w3-k8s-1.25.0: Checking for guest additions in VM...
w3-k8s-1.25.0: The guest additions on this VM do not match the installed version of
w3-k8s-1.25.0: VirtualBox! In most cases this is fine, but in rare cases it can
w3-k8s-1.25.0: prevent things such as shared folders from working properly. If you see
w3-k8s-1.25.0: shared folder errors, please make sure the guest additions within the
w3-k8s-1.25.0: virtual machine match the version of VirtualBox you have installed on
w3-k8s-1.25.0: your host and reload your VM.
w3-k8s-1.25.0:
w3-k8s-1.25.0: Guest Additions Version: 5.2.12
w3-k8s-1.25.0: VirtualBox Version: 6.1
==> w3-k8s-1.25.0: Setting hostname...
==> w3-k8s-1.25.0: Configuring and enabling network interfaces...
==> w3-k8s-1.25.0: Running provisioner: shell...
w3-k8s-1.25.0: Running: /tmp/vagrant-shell20221101-5892-1o7k64u.sh
==> w3-k8s-1.25.0: Running provisioner: shell...
w3-k8s-1.25.0: Running: /tmp/vagrant-shell20221101-5892-1a62ito.sh
w3-k8s-1.25.0: Loaded plugins: fastestmirror
w3-k8s-1.25.0: Determining fastest mirrors
w3-k8s-1.25.0: * base: mirror.navercorp.com
w3-k8s-1.25.0: * extras: mirror.navercorp.com
w3-k8s-1.25.0: * updates: mirror.navercorp.com
w3-k8s-1.25.0: https://packages.cloud.google.com/yum/repos/kubernetes-el7-x86_64/repodata/repomd.xml: [Errno 14] curl#60 - "The certificate issuer's certificate has expired. Check your system date and time."
w3-k8s-1.25.0: Trying other mirror.
w3-k8s-1.25.0: It was impossible to connect to the CentOS servers.
w3-k8s-1.25.0: This could mean a connectivity issue in your environment, such as the requirement to configure a proxy,
w3-k8s-1.25.0: or a transparent proxy that tampers with TLS security, or an incorrect system clock.
w3-k8s-1.25.0: You can try to solve this issue by using the instructions on https://wiki.centos.org/yum-errors
w3-k8s-1.25.0: If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
w3-k8s-1.25.0:
w3-k8s-1.25.0:
w3-k8s-1.25.0:
w3-k8s-1.25.0: One of the configured repositories failed (Kubernetes),
w3-k8s-1.25.0: and yum doesn't have enough cached data to continue. At this point the only
w3-k8s-1.25.0: safe thing yum can do is fail. There are a few ways to work "fix" this:
w3-k8s-1.25.0:
w3-k8s-1.25.0: 1. Contact the upstream for the repository and get them to fix the problem.
w3-k8s-1.25.0:
w3-k8s-1.25.0: 2. Reconfigure the baseurl/etc. for the repository, to point to a working
w3-k8s-1.25.0: upstream. This is most often useful if you are using a newer
w3-k8s-1.25.0: distribution release than is supported by the repository (and the
w3-k8s-1.25.0: packages for the previous distribution release still work).
w3-k8s-1.25.0:
w3-k8s-1.25.0: 3. Run the command with the repository temporarily disabled
w3-k8s-1.25.0: yum --disablerepo=kubernetes ...
w3-k8s-1.25.0:
w3-k8s-1.25.0: 4. Disable the repository permanently, so yum won't use it by default. Yum
w3-k8s-1.25.0: will then just ignore the repository until you permanently enable it
w3-k8s-1.25.0: again or use --enablerepo for temporary usage:
w3-k8s-1.25.0:
w3-k8s-1.25.0: yum-config-manager --disable kubernetes
w3-k8s-1.25.0: or
w3-k8s-1.25.0: subscription-manager repos --disable=kubernetes
w3-k8s-1.25.0:
w3-k8s-1.25.0: 5. Configure the failing repository to be skipped, if it is unavailable.
w3-k8s-1.25.0: Note that yum will try to contact the repo. when it runs most commands,
w3-k8s-1.25.0: so will have to try and fail each time (and thus. yum will be be much
w3-k8s-1.25.0: slower). If it is a very temporary problem though, this is often a nice
w3-k8s-1.25.0: compromise:
w3-k8s-1.25.0:
w3-k8s-1.25.0: yum-config-manager --save --setopt=kubernetes.skip_if_unavailable=true
w3-k8s-1.25.0:
w3-k8s-1.25.0: failure: repodata/repomd.xml from kubernetes: [Errno 256] No more mirrors to try.
w3-k8s-1.25.0: https://packages.cloud.google.com/yum/repos/kubernetes-el7-x86_64/repodata/repomd.xml: [Errno 14] curl#60 - "The certificate issuer's certificate has expired. Check your system date and time."
w3-k8s-1.25.0: Loaded plugins: fastestmirror
w3-k8s-1.25.0: Loading mirror speeds from cached hostfile
w3-k8s-1.25.0: * base: mirror.navercorp.com
w3-k8s-1.25.0: * extras: mirror.navercorp.com
w3-k8s-1.25.0: * updates: mirror.navercorp.com
w3-k8s-1.25.0: https://packages.cloud.google.com/yum/repos/kubernetes-el7-x86_64/repodata/repomd.xml: [Errno 14] curl#60 - "The certificate issuer's certificate has expired. Check your system date and time."
w3-k8s-1.25.0: Trying other mirror.
w3-k8s-1.25.0: It was impossible to connect to the CentOS servers.
w3-k8s-1.25.0: This could mean a connectivity issue in your environment, such as the requirement to configure a proxy,
w3-k8s-1.25.0: or a transparent proxy that tampers with TLS security, or an incorrect system clock.
w3-k8s-1.25.0: You can try to solve this issue by using the instructions on https://wiki.centos.org/yum-errors
w3-k8s-1.25.0: If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
w3-k8s-1.25.0:
w3-k8s-1.25.0:
w3-k8s-1.25.0:
w3-k8s-1.25.0: One of the configured repositories failed (Kubernetes),
w3-k8s-1.25.0: and yum doesn't have enough cached data to continue. At this point the only
w3-k8s-1.25.0: safe thing yum can do is fail. There are a few ways to work "fix" this:
w3-k8s-1.25.0:
w3-k8s-1.25.0: 1. Contact the upstream for the repository and get them to fix the problem.
w3-k8s-1.25.0:
w3-k8s-1.25.0: 2. Reconfigure the baseurl/etc. for the repository, to point to a working
w3-k8s-1.25.0: upstream. This is most often useful if you are using a newer
w3-k8s-1.25.0: distribution release than is supported by the repository (and the
w3-k8s-1.25.0: packages for the previous distribution release still work).
w3-k8s-1.25.0:
w3-k8s-1.25.0: 3. Run the command with the repository temporarily disabled
w3-k8s-1.25.0: yum --disablerepo=kubernetes ...
w3-k8s-1.25.0:
w3-k8s-1.25.0: 4. Disable the repository permanently, so yum won't use it by default. Yum
w3-k8s-1.25.0: will then just ignore the repository until you permanently enable it
w3-k8s-1.25.0: again or use --enablerepo for temporary usage:
w3-k8s-1.25.0:
w3-k8s-1.25.0: yum-config-manager --disable kubernetes
w3-k8s-1.25.0: or
w3-k8s-1.25.0: subscription-manager repos --disable=kubernetes
w3-k8s-1.25.0:
w3-k8s-1.25.0: 5. Configure the failing repository to be skipped, if it is unavailable.
w3-k8s-1.25.0: Note that yum will try to contact the repo. when it runs most commands,
w3-k8s-1.25.0: so will have to try and fail each time (and thus. yum will be be much
w3-k8s-1.25.0: slower). If it is a very temporary problem though, this is often a nice
w3-k8s-1.25.0: compromise:
w3-k8s-1.25.0:
w3-k8s-1.25.0: yum-config-manager --save --setopt=kubernetes.skip_if_unavailable=true
w3-k8s-1.25.0:
w3-k8s-1.25.0: failure: repodata/repomd.xml from kubernetes: [Errno 256] No more mirrors to try.
w3-k8s-1.25.0: https://packages.cloud.google.com/yum/repos/kubernetes-el7-x86_64/repodata/repomd.xml: [Errno 14] curl#60 - "The certificate issuer's certificate has expired. Check your system date and time."
w3-k8s-1.25.0: Loaded plugins: fastestmirror
w3-k8s-1.25.0: Loading mirror speeds from cached hostfile
w3-k8s-1.25.0: * base: mirror.navercorp.com
w3-k8s-1.25.0: * extras: mirror.navercorp.com
w3-k8s-1.25.0: * updates: mirror.navercorp.com
w3-k8s-1.25.0: https://packages.cloud.google.com/yum/repos/kubernetes-el7-x86_64/repodata/repomd.xml: [Errno 14] curl#60 - "The certificate issuer's certificate has expired. Check your system date and time."
w3-k8s-1.25.0: Trying other mirror.
w3-k8s-1.25.0: It was impossible to connect to the CentOS servers.
w3-k8s-1.25.0: This could mean a connectivity issue in your environment, such as the requirement to configure a proxy,
w3-k8s-1.25.0: or a transparent proxy that tampers with TLS security, or an incorrect system clock.
w3-k8s-1.25.0: You can try to solve this issue by using the instructions on https://wiki.centos.org/yum-errors
w3-k8s-1.25.0: If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
w3-k8s-1.25.0:
w3-k8s-1.25.0:
w3-k8s-1.25.0:
w3-k8s-1.25.0: One of the configured repositories failed (Kubernetes),
w3-k8s-1.25.0: and yum doesn't have enough cached data to continue. At this point the only
w3-k8s-1.25.0: safe thing yum can do is fail. There are a few ways to work "fix" this:
w3-k8s-1.25.0:
w3-k8s-1.25.0: 1. Contact the upstream for the repository and get them to fix the problem.
w3-k8s-1.25.0:
w3-k8s-1.25.0: 2. Reconfigure the baseurl/etc. for the repository, to point to a working
w3-k8s-1.25.0: upstream. This is most often useful if you are using a newer
w3-k8s-1.25.0: distribution release than is supported by the repository (and the
w3-k8s-1.25.0: packages for the previous distribution release still work).
w3-k8s-1.25.0:
w3-k8s-1.25.0: 3. Run the command with the repository temporarily disabled
w3-k8s-1.25.0: yum --disablerepo=kubernetes ...
w3-k8s-1.25.0:
w3-k8s-1.25.0: 4. Disable the repository permanently, so yum won't use it by default. Yum
w3-k8s-1.25.0: will then just ignore the repository until you permanently enable it
w3-k8s-1.25.0: again or use --enablerepo for temporary usage:
w3-k8s-1.25.0:
w3-k8s-1.25.0: yum-config-manager --disable kubernetes
w3-k8s-1.25.0: or
w3-k8s-1.25.0: subscription-manager repos --disable=kubernetes
w3-k8s-1.25.0:
w3-k8s-1.25.0: 5. Configure the failing repository to be skipped, if it is unavailable.
w3-k8s-1.25.0: Note that yum will try to contact the repo. when it runs most commands,
w3-k8s-1.25.0: so will have to try and fail each time (and thus. yum will be be much
w3-k8s-1.25.0: slower). If it is a very temporary problem though, this is often a nice
w3-k8s-1.25.0: compromise:
w3-k8s-1.25.0:
w3-k8s-1.25.0: yum-config-manager --save --setopt=kubernetes.skip_if_unavailable=true
w3-k8s-1.25.0:
w3-k8s-1.25.0: failure: repodata/repomd.xml from kubernetes: [Errno 256] No more mirrors to try.
w3-k8s-1.25.0: https://packages.cloud.google.com/yum/repos/kubernetes-el7-x86_64/repodata/repomd.xml: [Errno 14] curl#60 - "The certificate issuer's certificate has expired. Check your system date and time."
w3-k8s-1.25.0: Loaded plugins: fastestmirror
w3-k8s-1.25.0: Loading mirror speeds from cached hostfile
w3-k8s-1.25.0: * base: mirror.navercorp.com
w3-k8s-1.25.0: * extras: mirror.navercorp.com
w3-k8s-1.25.0: * updates: mirror.navercorp.com
w3-k8s-1.25.0: https://packages.cloud.google.com/yum/repos/kubernetes-el7-x86_64/repodata/repomd.xml: [Errno 14] curl#60 - "The certificate issuer's certificate has expired. Check your system date and time."
w3-k8s-1.25.0: Trying other mirror.
w3-k8s-1.25.0: It was impossible to connect to the CentOS servers.
w3-k8s-1.25.0: This could mean a connectivity issue in your environment, such as the requirement to configure a proxy,
w3-k8s-1.25.0: or a transparent proxy that tampers with TLS security, or an incorrect system clock.
w3-k8s-1.25.0: You can try to solve this issue by using the instructions on https://wiki.centos.org/yum-errors
w3-k8s-1.25.0: If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
w3-k8s-1.25.0:
w3-k8s-1.25.0:
w3-k8s-1.25.0:
w3-k8s-1.25.0: One of the configured repositories failed (Kubernetes),
w3-k8s-1.25.0: and yum doesn't have enough cached data to continue. At this point the only
w3-k8s-1.25.0: safe thing yum can do is fail. There are a few ways to work "fix" this:
w3-k8s-1.25.0:
w3-k8s-1.25.0: 1. Contact the upstream for the repository and get them to fix the problem.
w3-k8s-1.25.0:
w3-k8s-1.25.0: 2. Reconfigure the baseurl/etc. for the repository, to point to a working
w3-k8s-1.25.0: upstream. This is most often useful if you are using a newer
w3-k8s-1.25.0: distribution release than is supported by the repository (and the
w3-k8s-1.25.0: packages for the previous distribution release still work).
w3-k8s-1.25.0:
w3-k8s-1.25.0: 3. Run the command with the repository temporarily disabled
w3-k8s-1.25.0: yum --disablerepo=kubernetes ...
w3-k8s-1.25.0:
w3-k8s-1.25.0: 4. Disable the repository permanently, so yum won't use it by default. Yum
w3-k8s-1.25.0: will then just ignore the repository until you permanently enable it
w3-k8s-1.25.0: again or use --enablerepo for temporary usage:
w3-k8s-1.25.0:
w3-k8s-1.25.0: yum-config-manager --disable kubernetes
w3-k8s-1.25.0: or
w3-k8s-1.25.0: subscription-manager repos --disable=kubernetes
w3-k8s-1.25.0:
w3-k8s-1.25.0: 5. Configure the failing repository to be skipped, if it is unavailable.
w3-k8s-1.25.0: Note that yum will try to contact the repo. when it runs most commands,
w3-k8s-1.25.0: so will have to try and fail each time (and thus. yum will be be much
w3-k8s-1.25.0: slower). If it is a very temporary problem though, this is often a nice
w3-k8s-1.25.0: compromise:
w3-k8s-1.25.0:
w3-k8s-1.25.0: yum-config-manager --save --setopt=kubernetes.skip_if_unavailable=true
w3-k8s-1.25.0:
w3-k8s-1.25.0: failure: repodata/repomd.xml from kubernetes: [Errno 256] No more mirrors to try.
w3-k8s-1.25.0: https://packages.cloud.google.com/yum/repos/kubernetes-el7-x86_64/repodata/repomd.xml: [Errno 14] curl#60 - "The certificate issuer's certificate has expired. Check your system date and time."
w3-k8s-1.25.0: Loaded plugins: fastestmirror
w3-k8s-1.25.0: adding repo from: https://download.docker.com/linux/centos/docker-ce.repo
w3-k8s-1.25.0: grabbing file https://download.docker.com/linux/centos/docker-ce.repo to /etc/yum.repos.d/docker-ce.repo
w3-k8s-1.25.0: Could not fetch/save url https://download.docker.com/linux/centos/docker-ce.repo to file /etc/yum.repos.d/docker-ce.repo: [Errno 14] curl#60 - "The certificate issuer's certificate has expired. Check your system date and time."
w3-k8s-1.25.0: Loaded plugins: fastestmirror
w3-k8s-1.25.0: Loading mirror speeds from cached hostfile
w3-k8s-1.25.0: * base: mirror.navercorp.com
w3-k8s-1.25.0: * extras: mirror.navercorp.com
w3-k8s-1.25.0: * updates: mirror.navercorp.com
w3-k8s-1.25.0: https://packages.cloud.google.com/yum/repos/kubernetes-el7-x86_64/repodata/repomd.xml: [Errno 14] curl#60 - "The certificate issuer's certificate has expired. Check your system date and time."
w3-k8s-1.25.0: Trying other mirror.
w3-k8s-1.25.0: It was impossible to connect to the CentOS servers.
w3-k8s-1.25.0: This could mean a connectivity issue in your environment, such as the requirement to configure a proxy,
w3-k8s-1.25.0: or a transparent proxy that tampers with TLS security, or an incorrect system clock.
w3-k8s-1.25.0: You can try to solve this issue by using the instructions on https://wiki.centos.org/yum-errors
w3-k8s-1.25.0: If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
w3-k8s-1.25.0:
w3-k8s-1.25.0:
w3-k8s-1.25.0:
w3-k8s-1.25.0: One of the configured repositories failed (Kubernetes),
w3-k8s-1.25.0: and yum doesn't have enough cached data to continue. At this point the only
w3-k8s-1.25.0: safe thing yum can do is fail. There are a few ways to work "fix" this:
w3-k8s-1.25.0:
w3-k8s-1.25.0: 1. Contact the upstream for the repository and get them to fix the problem.
w3-k8s-1.25.0:
w3-k8s-1.25.0: 2. Reconfigure the baseurl/etc. for the repository, to point to a working
w3-k8s-1.25.0: upstream. This is most often useful if you are using a newer
w3-k8s-1.25.0: distribution release than is supported by the repository (and the
w3-k8s-1.25.0: packages for the previous distribution release still work).
w3-k8s-1.25.0:
w3-k8s-1.25.0: 3. Run the command with the repository temporarily disabled
w3-k8s-1.25.0: yum --disablerepo=kubernetes ...
w3-k8s-1.25.0:
w3-k8s-1.25.0: 4. Disable the repository permanently, so yum won't use it by default. Yum
w3-k8s-1.25.0: will then just ignore the repository until you permanently enable it
w3-k8s-1.25.0: again or use --enablerepo for temporary usage:
w3-k8s-1.25.0:
w3-k8s-1.25.0: yum-config-manager --disable kubernetes
w3-k8s-1.25.0: or
w3-k8s-1.25.0: subscription-manager repos --disable=kubernetes
w3-k8s-1.25.0:
w3-k8s-1.25.0: 5. Configure the failing repository to be skipped, if it is unavailable.
w3-k8s-1.25.0: Note that yum will try to contact the repo. when it runs most commands,
w3-k8s-1.25.0: so will have to try and fail each time (and thus. yum will be be much
w3-k8s-1.25.0: slower). If it is a very temporary problem though, this is often a nice
w3-k8s-1.25.0: compromise:
w3-k8s-1.25.0:
w3-k8s-1.25.0: yum-config-manager --save --setopt=kubernetes.skip_if_unavailable=true
w3-k8s-1.25.0:
w3-k8s-1.25.0: failure: repodata/repomd.xml from kubernetes: [Errno 256] No more mirrors to try.
w3-k8s-1.25.0: https://packages.cloud.google.com/yum/repos/kubernetes-el7-x86_64/repodata/repomd.xml: [Errno 14] curl#60 - "The certificate issuer's certificate has expired. Check your system date and time."
w3-k8s-1.25.0: Loaded plugins: fastestmirror
w3-k8s-1.25.0: Loading mirror speeds from cached hostfile
w3-k8s-1.25.0: * base: mirror.navercorp.com
w3-k8s-1.25.0: * extras: mirror.navercorp.com
w3-k8s-1.25.0: * updates: mirror.navercorp.com
w3-k8s-1.25.0: https://packages.cloud.google.com/yum/repos/kubernetes-el7-x86_64/repodata/repomd.xml: [Errno 14] curl#60 - "The certificate issuer's certificate has expired. Check your system date and time."
w3-k8s-1.25.0: Trying other mirror.
w3-k8s-1.25.0: It was impossible to connect to the CentOS servers.
w3-k8s-1.25.0: This could mean a connectivity issue in your environment, such as the requirement to configure a proxy,
w3-k8s-1.25.0: or a transparent proxy that tampers with TLS security, or an incorrect system clock.
w3-k8s-1.25.0: You can try to solve this issue by using the instructions on https://wiki.centos.org/yum-errors
w3-k8s-1.25.0: If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
w3-k8s-1.25.0:
w3-k8s-1.25.0:
w3-k8s-1.25.0:
w3-k8s-1.25.0: One of the configured repositories failed (Kubernetes),
w3-k8s-1.25.0: and yum doesn't have enough cached data to continue. At this point the only
w3-k8s-1.25.0: safe thing yum can do is fail. There are a few ways to work "fix" this:
w3-k8s-1.25.0:
w3-k8s-1.25.0: 1. Contact the upstream for the repository and get them to fix the problem.
w3-k8s-1.25.0:
w3-k8s-1.25.0: 2. Reconfigure the baseurl/etc. for the repository, to point to a working
w3-k8s-1.25.0: upstream. This is most often useful if you are using a newer
w3-k8s-1.25.0: distribution release than is supported by the repository (and the
w3-k8s-1.25.0: packages for the previous distribution release still work).
w3-k8s-1.25.0:
w3-k8s-1.25.0: 3. Run the command with the repository temporarily disabled
w3-k8s-1.25.0: yum --disablerepo=kubernetes ...
w3-k8s-1.25.0:
w3-k8s-1.25.0: 4. Disable the repository permanently, so yum won't use it by default. Yum
w3-k8s-1.25.0: will then just ignore the repository until you permanently enable it
w3-k8s-1.25.0: again or use --enablerepo for temporary usage:
w3-k8s-1.25.0:
w3-k8s-1.25.0: yum-config-manager --disable kubernetes
w3-k8s-1.25.0: or
w3-k8s-1.25.0: subscription-manager repos --disable=kubernetes
w3-k8s-1.25.0:
w3-k8s-1.25.0: 5. Configure the failing repository to be skipped, if it is unavailable.
w3-k8s-1.25.0: Note that yum will try to contact the repo. when it runs most commands,
w3-k8s-1.25.0: so will have to try and fail each time (and thus. yum will be be much
w3-k8s-1.25.0: slower). If it is a very temporary problem though, this is often a nice
w3-k8s-1.25.0: compromise:
w3-k8s-1.25.0:
w3-k8s-1.25.0: yum-config-manager --save --setopt=kubernetes.skip_if_unavailable=true
w3-k8s-1.25.0:
w3-k8s-1.25.0: failure: repodata/repomd.xml from kubernetes: [Errno 256] No more mirrors to try.
w3-k8s-1.25.0: https://packages.cloud.google.com/yum/repos/kubernetes-el7-x86_64/repodata/repomd.xml: [Errno 14] curl#60 - "The certificate issuer's certificate has expired. Check your system date and time."
w3-k8s-1.25.0: /tmp/vagrant-shell: line 21: /etc/containerd/config.toml: No such file or directory
w3-k8s-1.25.0: Failed to execute operation: No such file or directory
w3-k8s-1.25.0: Failed to execute operation: No such file or directory
w3-k8s-1.25.0: Failed to execute operation: No such file or directory
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.
답변
답변을 기다리고 있는 질문이에요
첫번째 답변을 남겨보세요!