Also, I’ve been getting a lot of these microceph entries in syslog.
Turns out microceph wasn’t initialized (good, I have no use for it), so maybe that’s why.
It safe to remove microceph snapd? I looked at initialization options and I guess it’s part of normal init defaults (which it probably shouldn’t be, but as long as it can be removed that’s fine).
microceph.daemon[37337]:
time="2024-04-24T13:17:58+08:00"
level=debug
msg="start: database not ready, waiting..."
Environment:
$ sudo snap list | grep ceph
microceph 18.2.0+snap450240f5dd 975 latest/stable canonical** -
$ incus --version
0.6
$ sudo incus profile show default
config: {}
description: Default Incus profile
devices:
eth0:
name: eth0
nictype: bridged
parent: br0
type: nic
root:
path: /
pool: default
type: disk
name: default
$ uname -a # Mint 21.3 (22.04 LTS)
Linux 5.15.0-105-generic #115-Ubuntu SMP Mon Apr 15 09:52:04 UTC 2024
It looks like you’ve chosen the “daily” repo (described as “untested daily builds” in the documentation), so you just get a timestamp as the version number.
For comparison, I’m on the 6.0 LTS branch:
root@nuc3:~# cat /etc/apt/sources.list.d/zabbly-incus-lts-6.0.sources
Enabled: yes
Types: deb
URIs: https://pkgs.zabbly.com/incus/lts-6.0
Suites: jammy
Components: main
Architectures: amd64
Signed-By: /etc/apt/keyrings/zabbly.asc
I’d suggest you use either this or the “stable” branch, unless you’re hacking on the very edge of incus.
EDIT: also, you’re right that incus has no dependency on microceph (unless you’ve configured a ceph storage pool of course), or indeed any other snap, so you’re free to delete it. Uninstall snapd too if you’re not using any other snaps.