Two versions of lxd same time?

LXD
1

Hi,

I have an in house server that’s not connected to the internet, until nov 12, and lxd got updated to 3.18, looking at the log, there are two versions mounting: 10343 and 12317, any idea why?

when the lxd updated from revision 10343 to 12317, do we have to update the container as well?

Thanks

Oct 31 08:51:21 fifi systemd[1]: Mounting Mount unit for lxd, revision 10343…
Nov 04 06:44:40 fifi systemd[1]: Mounting Mount unit for lxd, revision 10343…
Nov 05 06:42:25 fifi systemd[1]: Mounting Mount unit for lxd, revision 10343…
Nov 06 06:51:47 fifi systemd[1]: Mounting Mount unit for lxd, revision 10343…
Nov 07 06:45:45 fifi systemd[1]: Mounting Mount unit for lxd, revision 10343…
Nov 08 06:41:42 fifi systemd[1]: Mounting Mount unit for lxd, revision 10343…
Nov 09 06:07:55 fifi systemd[1]: Mounting Mount unit for lxd, revision 10343…
Nov 11 06:57:49 fifi systemd[1]: Mounting Mount unit for lxd, revision 10343…
Nov 12 06:43:32 fifi systemd[1]: Mounting Mount unit for lxd, revision 10343…
Nov 12 16:05:20 fifi systemd[1]: Mounting Mount unit for lxd, revision 12317…
Nov 13 06:47:52 fifi systemd[1]: Mounting Mount unit for lxd, revision 10343…
Nov 13 10:40:19 fifi systemd[1]: Mounting Mount unit for lxd, revision 12317…
Nov 14 05:53:18 fifi systemd[1]: Mounting Mount unit for lxd, revision 10343…
Nov 14 05:53:18 fifi systemd[1]: Mounting Mount unit for lxd, revision 12317…
Nov 15 06:28:41 fifi systemd[1]: Mounting Mount unit for lxd, revision 12317…
Nov 15 06:28:41 fifi systemd[1]: Mounting Mount unit for lxd, revision 10343…
Nov 16 06:35:26 fifi systemd[1]: Mounting Mount unit for lxd, revision 12317…
Nov 16 06:35:26 fifi systemd[1]: Mounting Mount unit for lxd, revision 10343…
Nov 17 07:44:59 fifi systemd[1]: Mounting Mount unit for lxd, revision 10343…
Nov 17 07:44:59 fifi systemd[1]: Mounting Mount unit for lxd, revision 12317…
Nov 17 08:32:25 fifi systemd[1]: Mounting Mount unit for lxd, revision 10343…
Nov 17 08:32:25 fifi systemd[1]: Mounting Mount unit for lxd, revision 12317…
Nov 17 23:49:39 fifi systemd[1]: Mounting Mount unit for lxd, revision 12317…
Nov 17 23:49:39 fifi systemd[1]: Mounting Mount unit for lxd, revision 10343…
Nov 17 23:57:12 fifi systemd[1]: Mounting Mount unit for lxd, revision 12317…
Nov 17 23:57:12 fifi systemd[1]: Mounting Mount unit for lxd, revision 10343…
Nov 18 00:00:30 fifi systemd[1]: Mounting Mount unit for lxd, revision 10343…
Nov 18 00:00:30 fifi systemd[1]: Mounting Mount unit for lxd, revision 12317…
Nov 18 00:19:49 fifi systemd[1]: Mounting Mount unit for lxd, revision 10343…
Nov 18 00:19:49 fifi systemd[1]: Mounting Mount unit for lxd, revision 12317…
Nov 18 00:43:38 fifi systemd[1]: Mounting Mount unit for lxd, revision 10343…
Nov 18 00:43:38 fifi systemd[1]: Mounting Mount unit for lxd, revision 12317…

2

Hi!

This is a snap question. When you install a snap package (in this case, LXD), then snapd is managing the updates.

When an update is available, snapd schedules to update it, anytime within 24 hours. You can configure snapd to delay this, or perform the update during the small hours. The containers do not restart when LXD is updated, but any lxc exec connections will disconnect.

Older versions stay available, and you can use a feature of snapd to revert to the previous version if needed. These two (or more) versions are not active at the same time. Just one of them.

3

but why two mounting happens in the same time (00:43:38) , one is revision 10343 another is 12317? thanks

4

this is not a lxd journal, this is a systemd journal. Systemd is not trying to keep you informed about the current LXD version, it is informing you of the file system it is mounting. As SNAP keeps 2 versions around for LXD (don’t know why since LXD devs have clearly said that they DO NOT support reverts), there are 2 mounts and each one can give you a pointer on current state of LXD, since SNAP journal is less than useful here. You can assume that the highest number is the currently running version (unless there is a catastrophic failure, in this case nothing works anyway)