snap version of docker stopped on several VMs all of a sudden.
Is snap trying an update of itself?
Messages i get:
Jul 27 06:35:57 xxx systemd[1]: Stopping Docker Application Container Engine...
-- Subject: A stop job for unit docker.service has begun execution
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- A stop job for unit docker.service has begun execution.
--
-- The job identifier is 163063.
Jul 27 06:35:57 xxx dockerd[2421]: time="2021-07-27T06:35:57.933618289Z" level=info msg="Processing signal 'terminated'"
Jul 27 06:35:58 xxx dockerd[2421]: time="2021-07-27T06:35:58.116153879Z" level=info msg="ignoring event" module=libcontainerd namespace=moby topic=/tasks/delete type="*events.TaskDelete"
Jul 27 06:35:59 xxx dockerd[2421]: time="2021-07-27T06:35:59.558634050Z" level=info msg="ignoring event" module=libcontainerd namespace=moby topic=/tasks/delete type="*events.TaskDelete"
Jul 27 06:36:07 xxx dockerd[2421]: time="2021-07-27T06:36:07.958665748Z" level=info msg="Container 1f524a74e371ae8d5dc979d577e7c20f943e6121637782b83b89ef0ddbb87b99 failed to exit within 10 seconds of signal 15 - using the force"
Jul 27 06:36:07 xxx dockerd[2421]: time="2021-07-27T06:36:07.958862689Z" level=info msg="Container 15db7363843db715b1f1f0a856980c04d887cf34a2f9a1bc454597e0e45da542 failed to exit within 10 seconds of signal 15 - using the force"
Jul 27 06:36:07 xxx dockerd[2421]: time="2021-07-27T06:36:07.959743590Z" level=info msg="Container e53bebe1fd1839755f2f13ac7d31a783a9abfbbb593fd5caa59ee8acccff1cc3 failed to exit within 10 seconds of signal 15 - using the force"
Jul 27 06:36:08 xxx dockerd[2421]: time="2021-07-27T06:36:08.102458416Z" level=info msg="ignoring event" module=libcontainerd namespace=moby topic=/tasks/delete type="*events.TaskDelete"
Jul 27 06:36:08 xxx dockerd[2421]: time="2021-07-27T06:36:08.155778483Z" level=info msg="ignoring event" module=libcontainerd namespace=moby topic=/tasks/delete type="*events.TaskDelete"
Jul 27 06:36:08 xxx dockerd[2421]: time="2021-07-27T06:36:08.313277500Z" level=info msg="ignoring event" module=libcontainerd namespace=moby topic=/tasks/delete type="*events.TaskDelete"
Jul 27 06:36:08 xxx dockerd[2421]: time="2021-07-27T06:36:08.682723587Z" level=info msg="stopping event stream following graceful shutdown" error="<nil>" module=libcontainerd namespace=moby
Jul 27 06:36:08 xxx dockerd[2421]: time="2021-07-27T06:36:08.683934421Z" level=info msg="Daemon shutdown complete"
Jul 27 06:36:08 xxx systemd[1]: docker.service: Succeeded.
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- The unit docker.service has successfully entered the 'dead' state.
Jul 27 06:36:08 xxx systemd[1]: Stopped Docker Application Container Engine.
-- Subject: A stop job for unit docker.service has finished
services:
docker.dockerd: simple, enabled, active
snap-id: xxx
tracking: latest/stable
refresh-date: today at 10:18 UTC
channels:
latest/stable: 20.10.8 2021-08-27 (1125) 122MB -
latest/candidate: 20.10.8 2021-08-26 (1125) 122MB -
latest/beta: 20.10.8 2021-08-26 (1182) 121MB -
latest/edge: 20.10.8 2021-08-31 (1189) 121MB -
17.03/stable: 17.03.2-ce-1 2017-07-20 (159) 42MB -
17.03/candidate: 17.03.2-ce-1 2017-06-30 (159) 42MB -
17.03/beta: ↑
17.03/edge: 17.03.2-ce-1 2017-06-30 (159) 42MB -
installed: 19.03.13 (796) 137MB -
Thanks in advance,
Bodo
It seems that a wrong parameter caused the inability of docker daemon to restart correctly.
It seems that snap tries to update docker once a day and if there is an update it will be done restarting the containers if they have the restart flag.
Is it true that there is no way to stop snap from updating and restarting the docker/containerd?
