osmc@HTPC:~$ sudo /usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock
INFO[2020-09-23T07:11:57.491682609+01:00] Starting up
failed to load listeners: no sockets found via socket activation: make sure the service was started by systemd
I won’t have physical access to my OSMC devices until the weekend. At that point, I could try a fresh install, install Docker and upgrade to Buster.
I did a bit of searching for the error “failed to load listeners: no sockets found via socket activation: make sure the service was started by systemd”. See if this helps:
This explains why -H fd:// is inappropriate from the command line:
Cheers for that. A lot of it is over my head but I did find this in /etc/systemd/system/sockets.target.wants
[Unit]
Description=Docker Socket for the API
PartOf=docker.service
[Socket]
ListenStream=/var/run/docker.sock
SocketMode=0660
SocketUser=root
SocketGroup=docker
[Install]
WantedBy=sockets.target
Running on
Raspberry Pi Model B Plus Rev 1.2
Update done (after editing sources) from OsMC add-on.
Accessing remote MySQL database and content over SMB.
I hadn’t really noticed that you were also running the new 4.9 kernel, so, although this is a Buster testing thread, your problem might be kernel-related – or a combination of kernel and OS.
I’ve been informed in no uncertain terms that performing experimental updates on our one and only Vero4K could result in my head on a plate. I’ll certainly try it on my Pi3 but the Vero4K is off the menu, I’m afraid. Apologies.
praised too quickly
I have some problems on samba. Anyone have an idea? One partition is visibled but I cannot connect there. Two others partitions works fine.
I have ssd + sdcard: