質問編集履歴
2
Dockerバージョンの追記
title
CHANGED
File without changes
|
body
CHANGED
@@ -4,6 +4,39 @@
|
|
4
4
|
MacOS 11.2.3
|
5
5
|
Docker 20.10.6
|
6
6
|
|
7
|
+
#Docker for Macバージョン
|
8
|
+
```
|
9
|
+
Client:
|
10
|
+
Cloud integration: 1.0.14
|
11
|
+
Version: 20.10.6
|
12
|
+
API version: 1.41
|
13
|
+
Go version: go1.16.3
|
14
|
+
Git commit: 370c289
|
15
|
+
Built: Fri Apr 9 22:46:57 2021
|
16
|
+
OS/Arch: darwin/arm64
|
17
|
+
Context: default
|
18
|
+
Experimental: true
|
19
|
+
|
20
|
+
Server: Docker Engine - Community
|
21
|
+
Engine:
|
22
|
+
Version: 20.10.6
|
23
|
+
API version: 1.41 (minimum version 1.12)
|
24
|
+
Go version: go1.13.15
|
25
|
+
Git commit: 8728dd2
|
26
|
+
Built: Fri Apr 9 22:44:13 2021
|
27
|
+
OS/Arch: linux/arm64
|
28
|
+
Experimental: false
|
29
|
+
containerd:
|
30
|
+
Version: 1.4.4
|
31
|
+
GitCommit: 05f951a3781f4f2c1911b05e61c160e9c30eaa8e
|
32
|
+
runc:
|
33
|
+
Version: 1.0.0-rc93
|
34
|
+
GitCommit: 12644e614e25b05da6fd08a38ffa0cfe1903fdec
|
35
|
+
docker-init:
|
36
|
+
Version: 0.19.0
|
37
|
+
GitCommit: de40ad0
|
38
|
+
```
|
39
|
+
|
7
40
|
## 質問
|
8
41
|
下記Dockefile内でyum -y install httpdを実行中に、404エラーが出てしまいました。
|
9
42
|
```
|
1
頂いたコメントをもとに補足
title
CHANGED
File without changes
|
body
CHANGED
@@ -79,4 +79,54 @@
|
|
79
79
|
|
80
80
|
おそらく、参照しているURLが古いままになっているようなので、ここを設定し直すことで解決できるのでは・・?
|
81
81
|
と思っていますが、解決できる方法があれば教えてきただけると助かります。
|
82
|
-
Linuxの知識不足もあり解決に時間がかかっております。
|
82
|
+
Linuxの知識不足もあり解決に時間がかかっております。
|
83
|
+
|
84
|
+
## 補足
|
85
|
+
|
86
|
+
Dockefile内の下記記述を修正し実行したがエラーは解消されず。
|
87
|
+
```
|
88
|
+
#FROM centos:7
|
89
|
+
FROM --platform=linux/x86_64 centos:7
|
90
|
+
```
|
91
|
+
|
92
|
+
エラー内容
|
93
|
+
|
94
|
+
``` => ERROR [ 8/12] RUN yum -y install wget 2.7s
|
95
|
+
------
|
96
|
+
> [ 8/12] RUN yum -y install wget:
|
97
|
+
#11 0.731 Loaded plugins: fastestmirror, ovl
|
98
|
+
#11 1.125 Determining fastest mirrors
|
99
|
+
#11 2.624
|
100
|
+
#11 2.624
|
101
|
+
#11 2.624 One of the configured repositories failed (Unknown),
|
102
|
+
#11 2.624 and yum doesn't have enough cached data to continue. At this point the only
|
103
|
+
#11 2.624 safe thing yum can do is fail. There are a few ways to work "fix" this:
|
104
|
+
#11 2.624
|
105
|
+
#11 2.624 1. Contact the upstream for the repository and get them to fix the problem.
|
106
|
+
#11 2.624
|
107
|
+
#11 2.624 2. Reconfigure the baseurl/etc. for the repository, to point to a working
|
108
|
+
#11 2.624 upstream. This is most often useful if you are using a newer
|
109
|
+
#11 2.624 distribution release than is supported by the repository (and the
|
110
|
+
#11 2.624 packages for the previous distribution release still work).
|
111
|
+
#11 2.624
|
112
|
+
#11 2.624 3. Run the command with the repository temporarily disabled
|
113
|
+
#11 2.624 yum --disablerepo=<repoid> ...
|
114
|
+
#11 2.624
|
115
|
+
#11 2.624 4. Disable the repository permanently, so yum won't use it by default. Yum
|
116
|
+
#11 2.624 will then just ignore the repository until you permanently enable it
|
117
|
+
#11 2.624 again or use --enablerepo for temporary usage:
|
118
|
+
#11 2.624
|
119
|
+
#11 2.624 yum-config-manager --disable <repoid>
|
120
|
+
#11 2.624 or
|
121
|
+
#11 2.624 subscription-manager repos --disable=<repoid>
|
122
|
+
#11 2.624
|
123
|
+
#11 2.624 5. Configure the failing repository to be skipped, if it is unavailable.
|
124
|
+
#11 2.624 Note that yum will try to contact the repo. when it runs most commands,
|
125
|
+
#11 2.624 so will have to try and fail each time (and thus. yum will be be much
|
126
|
+
#11 2.624 slower). If it is a very temporary problem though, this is often a nice
|
127
|
+
#11 2.624 compromise:
|
128
|
+
#11 2.624
|
129
|
+
#11 2.624 yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
|
130
|
+
#11 2.624
|
131
|
+
#11 2.624 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
|
132
|
+
```
|