質問編集履歴

2

sudo service docker status実行結果を追記させていただきました。

2019/04/19 07:18

投稿

退会済みユーザー
test CHANGED
File without changes
test CHANGED
@@ -197,3 +197,33 @@
197
197
  Apr 19 06:45:55 doc4 sudo[5146]: ubuntu : TTY=pts/2 ; PWD=/home/ubuntu ; USER=root ; COMMAND=/bin/journalctl -xe
198
198
 
199
199
  Apr 19 06:45:55 doc4 sudo[5146]: pam_unix(sudo:session): session opened for user root by ubuntu(uid=0)
200
+
201
+
202
+
203
+ sudo service docker status
204
+
205
+ ● docker.service - Docker Application Container Engine
206
+
207
+ Loaded: loaded (/lib/systemd/system/docker.service; disabled; vendor preset: enabled)
208
+
209
+ Active: failed (Result: exit-code) since Fri 2019-04-19 06:44:55 UTC; 29min ago
210
+
211
+ Docs: https://docs.docker.com
212
+
213
+ Process: 5022 ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock (code=exited, status=1/FAILURE)
214
+
215
+ Main PID: 5022 (code=exited, status=1/FAILURE)
216
+
217
+
218
+
219
+ Apr 19 06:44:55 doc4 systemd[1]: docker.service: Service hold-off time over, scheduling restart.
220
+
221
+ Apr 19 06:44:55 doc4 systemd[1]: docker.service: Scheduled restart job, restart counter is at 3.
222
+
223
+ Apr 19 06:44:55 doc4 systemd[1]: Stopped Docker Application Container Engine.
224
+
225
+ Apr 19 06:44:55 doc4 systemd[1]: docker.service: Start request repeated too quickly.
226
+
227
+ Apr 19 06:44:55 doc4 systemd[1]: docker.service: Failed with result 'exit-code'.
228
+
229
+ Apr 19 06:44:55 doc4 systemd[1]: Failed to start Docker Application Container Engine.

1

journalctl-xeを実行した際のコードを追記させていただきました。

2019/04/19 07:18

投稿

退会済みユーザー
test CHANGED
File without changes
test CHANGED
@@ -135,3 +135,65 @@
135
135
  ~$sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 23E7166788B63E1E
136
136
 
137
137
  を実行しています。
138
+
139
+
140
+
141
+ journalctl-xeを実行すると以下が表示されます
142
+
143
+ -- Subject: Unit docker.socket has begun start-up
144
+
145
+ -- Defined-By: systemd
146
+
147
+ -- Support: http://www.ubuntu.com/support
148
+
149
+ --
150
+
151
+ -- Unit docker.socket has begun starting up.
152
+
153
+ Apr 19 06:44:55 doc4 systemd[1]: Listening on Docker Socket for the API.
154
+
155
+ -- Subject: Unit docker.socket has finished start-up
156
+
157
+ -- Defined-By: systemd
158
+
159
+ -- Support: http://www.ubuntu.com/support
160
+
161
+ --
162
+
163
+ -- Unit docker.socket has finished starting up.
164
+
165
+ --
166
+
167
+ -- The start-up result is RESULT.
168
+
169
+ Apr 19 06:44:55 doc4 systemd[1]: docker.service: Start request repeated too quickly.
170
+
171
+ Apr 19 06:44:55 doc4 systemd[1]: docker.service: Failed with result 'exit-code'.
172
+
173
+ Apr 19 06:44:55 doc4 systemd[1]: Failed to start Docker Application Container Engine.
174
+
175
+ -- Subject: Unit docker.service has failed
176
+
177
+ -- Defined-By: systemd
178
+
179
+ -- Support: http://www.ubuntu.com/support
180
+
181
+ --
182
+
183
+ -- Unit docker.service has failed.
184
+
185
+ --
186
+
187
+ -- The result is RESULT.
188
+
189
+ Apr 19 06:44:55 doc4 systemd[1]: docker.socket: Failed with result 'service-start-limit-hit'.
190
+
191
+ Apr 19 06:45:01 doc4 CRON[5068]: pam_unix(cron:session): session opened for user root by (uid=0)
192
+
193
+ Apr 19 06:45:01 doc4 CRON[5069]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
194
+
195
+ Apr 19 06:45:01 doc4 CRON[5068]: pam_unix(cron:session): session closed for user root
196
+
197
+ Apr 19 06:45:55 doc4 sudo[5146]: ubuntu : TTY=pts/2 ; PWD=/home/ubuntu ; USER=root ; COMMAND=/bin/journalctl -xe
198
+
199
+ Apr 19 06:45:55 doc4 sudo[5146]: pam_unix(sudo:session): session opened for user root by ubuntu(uid=0)