質問編集履歴

2

Dockerバージョンの追記

2021/05/25 05:48

投稿

user202102
test CHANGED
File without changes
test CHANGED
@@ -10,6 +10,72 @@
10
10
 
11
11
 
12
12
 
13
+ #Docker for Macバージョン
14
+
15
+ ```
16
+
17
+ Client:
18
+
19
+ Cloud integration: 1.0.14
20
+
21
+ Version: 20.10.6
22
+
23
+ API version: 1.41
24
+
25
+ Go version: go1.16.3
26
+
27
+ Git commit: 370c289
28
+
29
+ Built: Fri Apr 9 22:46:57 2021
30
+
31
+ OS/Arch: darwin/arm64
32
+
33
+ Context: default
34
+
35
+ Experimental: true
36
+
37
+
38
+
39
+ Server: Docker Engine - Community
40
+
41
+ Engine:
42
+
43
+ Version: 20.10.6
44
+
45
+ API version: 1.41 (minimum version 1.12)
46
+
47
+ Go version: go1.13.15
48
+
49
+ Git commit: 8728dd2
50
+
51
+ Built: Fri Apr 9 22:44:13 2021
52
+
53
+ OS/Arch: linux/arm64
54
+
55
+ Experimental: false
56
+
57
+ containerd:
58
+
59
+ Version: 1.4.4
60
+
61
+ GitCommit: 05f951a3781f4f2c1911b05e61c160e9c30eaa8e
62
+
63
+ runc:
64
+
65
+ Version: 1.0.0-rc93
66
+
67
+ GitCommit: 12644e614e25b05da6fd08a38ffa0cfe1903fdec
68
+
69
+ docker-init:
70
+
71
+ Version: 0.19.0
72
+
73
+ GitCommit: de40ad0
74
+
75
+ ```
76
+
77
+
78
+
13
79
  ## 質問
14
80
 
15
81
  下記Dockefile内でyum -y install httpdを実行中に、404エラーが出てしまいました。

1

頂いたコメントをもとに補足

2021/05/25 05:48

投稿

user202102
test CHANGED
File without changes
test CHANGED
@@ -161,3 +161,103 @@
161
161
  と思っていますが、解決できる方法があれば教えてきただけると助かります。
162
162
 
163
163
  Linuxの知識不足もあり解決に時間がかかっております。
164
+
165
+
166
+
167
+ ## 補足
168
+
169
+
170
+
171
+ Dockefile内の下記記述を修正し実行したがエラーは解消されず。
172
+
173
+ ```
174
+
175
+ #FROM centos:7
176
+
177
+ FROM --platform=linux/x86_64 centos:7
178
+
179
+ ```
180
+
181
+
182
+
183
+ エラー内容
184
+
185
+
186
+
187
+ ``` => ERROR [ 8/12] RUN yum -y install wget 2.7s
188
+
189
+ ------
190
+
191
+ > [ 8/12] RUN yum -y install wget:
192
+
193
+ #11 0.731 Loaded plugins: fastestmirror, ovl
194
+
195
+ #11 1.125 Determining fastest mirrors
196
+
197
+ #11 2.624
198
+
199
+ #11 2.624
200
+
201
+ #11 2.624 One of the configured repositories failed (Unknown),
202
+
203
+ #11 2.624 and yum doesn't have enough cached data to continue. At this point the only
204
+
205
+ #11 2.624 safe thing yum can do is fail. There are a few ways to work "fix" this:
206
+
207
+ #11 2.624
208
+
209
+ #11 2.624 1. Contact the upstream for the repository and get them to fix the problem.
210
+
211
+ #11 2.624
212
+
213
+ #11 2.624 2. Reconfigure the baseurl/etc. for the repository, to point to a working
214
+
215
+ #11 2.624 upstream. This is most often useful if you are using a newer
216
+
217
+ #11 2.624 distribution release than is supported by the repository (and the
218
+
219
+ #11 2.624 packages for the previous distribution release still work).
220
+
221
+ #11 2.624
222
+
223
+ #11 2.624 3. Run the command with the repository temporarily disabled
224
+
225
+ #11 2.624 yum --disablerepo=<repoid> ...
226
+
227
+ #11 2.624
228
+
229
+ #11 2.624 4. Disable the repository permanently, so yum won't use it by default. Yum
230
+
231
+ #11 2.624 will then just ignore the repository until you permanently enable it
232
+
233
+ #11 2.624 again or use --enablerepo for temporary usage:
234
+
235
+ #11 2.624
236
+
237
+ #11 2.624 yum-config-manager --disable <repoid>
238
+
239
+ #11 2.624 or
240
+
241
+ #11 2.624 subscription-manager repos --disable=<repoid>
242
+
243
+ #11 2.624
244
+
245
+ #11 2.624 5. Configure the failing repository to be skipped, if it is unavailable.
246
+
247
+ #11 2.624 Note that yum will try to contact the repo. when it runs most commands,
248
+
249
+ #11 2.624 so will have to try and fail each time (and thus. yum will be be much
250
+
251
+ #11 2.624 slower). If it is a very temporary problem though, this is often a nice
252
+
253
+ #11 2.624 compromise:
254
+
255
+ #11 2.624
256
+
257
+ #11 2.624 yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
258
+
259
+ #11 2.624
260
+
261
+ #11 2.624 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
262
+
263
+ ```