Docker not starting after kernel update

[dragosde]

I just upgraded my Raspberry pi4 running Ubuntu to kernel Linux 5.15.0-1070-raspi on aarch64
After restarting, the only container that would not start was scrypted.

Ubuntu is 22.04.5 Linux 5.15.0-1070-raspi on aarch64 (not sure what kernel was there before but I guess 5.15.0-1068 )
Docker version is 20.10.5, build 55c4c88

I pulled the newest scrypted docker to make sure nothing is amiss

The Rpi4 also runs Homeasssistant docker but that is working fine.

Checking the container logs I find this:

s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service setup: starting
SCRYPTED_DOCKER_AVAHI != true, won't manage dbus nor avahi-daemon
s6-rc: info: service setup successfully started
s6-rc: info: service dbus: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
SCRYPTED_DOCKER_AVAHI != true, not starting dbus-daemon
s6-rc: info: service dbus successfully started
s6-rc: info: service avahi: starting
s6-rc: info: service avahi successfully started
SCRYPTED_DOCKER_AVAHI != true, not starting avahi-daemon
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
  #  node[83]: std::unique_ptr<long unsigned int> node::WorkerThreadsTaskRunner::DelayedTaskScheduler::Start() at ../src/node_platform.cc:68
  #  Assertion failed: (0) == (uv_thread_create(t.get(), start_thread, this))
----- Native stack trace -----
 1: 0xca9544 node::Assert(node::AssertionInfo const&) [node]
 2: 0xd1e8a4 node::WorkerThreadsTaskRunner::WorkerThreadsTaskRunner(int) [node]
 3: 0xd1e960 node::NodePlatform::NodePlatform(int, v8::TracingController*, v8::PageAllocator*) [node]
 4: 0xc636f8  [node]
 5: 0xc648ac node::Start(int, char**) [node]
 6: 0xffffa9a384c4  [/lib/aarch64-linux-gnu/libc.so.6]
 7: 0xffffa9a38598 __libc_start_main [/lib/aarch64-linux-gnu/libc.so.6]
 8: 0xbc3890  [node]
Aborted (core dumped)
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service avahi: stopping
s6-rc: info: service avahi successfully stopped
s6-rc: info: service dbus: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service dbus successfully stopped
s6-rc: info: service setup: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service setup successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped

I wonder if you guys got anything similar.

[dragosde]

Hey @koush I understand it's not the best moment as we are all getting ready to party :P but not sure this is a discussion. The docker doesn't start, Scrypted is actually down for me. The question about how it is going for other fellows was a rhetorical one, hoping someone can confirm they have the same issue. But I don't mind it being a discussion before it gets upgraded to a bug - unless it's only me.
Happy new year y'all!

[bjia56]

Try updating Docker. You may be running into this which can affect containers running newer versions of Ubuntu.

[dragosde]

Updating docker did the trick. Thanks!