[13:48] <adac> Hi there. I was wondering. Updating which of these packages would cause docker service to restart (ubuntu) https://pastebin.com/raw/HuxMjvNG  it is probably either containerd.io or  docker-ce-rootless-extras:amd64.
[13:49] <patdk-lap> well, docker depends on containerd.io so that will always do it
[13:51] <sdeziel> adac: you can check if any of those package's `.postinst` script does a restart `/var/lib/dpkg/info/<pkgname>.postinst`.
[13:51] <adac> patdk-lap, thank you very much!
[13:54] <patdk-lap> sdeziel, not really
[13:54] <patdk-lap> docker depends on After=network-online.target docker.socket firewalld.service containerd.service time-set.target
[13:54] <patdk-lap> so anything restarting those will cause it to restart
[13:55] <patdk-lap> containerd.io only restarts itself in postinit, but causes docker to restart
[13:57] <sdeziel> patdk-lap: oh, I thought that `After=` was just an ordering suggestion, not something that would affect other units like `Requires=`, `Requisite=` or `BindTo=`
[13:58] <patdk-lap> hmm, maybe
[13:58] <patdk-lap> but I do know docker restarts everytime containerio is updated
[13:58] <patdk-lap> and containerio is what actually runs docker, docker is just the *interface*
[13:59] <patdk-lap> likely too technical to care :)
[14:06] <sdeziel> yeah, but thanks for pointing out at systemd directives, that's something to keep in mind when tracking unexpected restarts
[14:26] <Guest89> Hello guys, I have problem getting lxdbr0 (LXD brige network) connect to my local network.. (192.168.0.x)
[14:28] <Guest89> Using LXD UI, i changed the ip configuration to 192.168.0.x to match with my local network.. but still my LXD vm can't be access from other machine in same network
[14:28] <Guest89> Can anyone guide me.
[14:38] <sdeziel> Guest89: please hop on #lxd :)
[14:40] <Guest89> ok, thank you for pointing out
[15:18] <runelind> I upgraded an LXD container to 22.04 and now I'm having issues with the MAC, and therefore DHCP address, changing every once in a while.  My friend said he ran into the same issue and it was something to do with netplan but he couldn't remember what.  Does this ring a bell for anyone? 
[16:54] <radix0> This is a half-help, half-rant question - when did the PDF for Ubuntu server become so terrible? I open it, all the bookmarks are broken, and topics I expect to be documented are not there (SNMPv3). I don't remember it being this awful.
[18:04] <tsimonq2> radix0: "PDF for Ubuntu server" is so ambiguous, nobody would even know how to start answering that ;)
[18:04] <tsimonq2> We have hundreds, if not thousands of packages, server and GUI, providing some kind of functionality related to PDFs.
[18:04] <rbasak> I assume it's the PDF from here: https://ubuntu.com/server/docs
[18:04] <rbasak> I understand the brokenness is being worked on.
[18:04] <tsimonq2> Ah, okay. :)
[18:05] <rbasak> SNMPv3 - sorry - the importance of this seems to have fallen below our "worth maintaining Ubuntu-server-specific docs for" threshold.
[18:05] <rbasak> radix0: ^
[18:12] <radix0> Yes - that's the PDF I am referring to. Why does SNMPv3 not make the cut?