Tom Parrott
Tom Parrott
They are all only distributed by snaps so we control the Go version, 1.21 should be fine.
@masnax any reason not to just switch to slog and avoid needing to dependent on LXD's logger (we will probably switch to slog too eventually), but for something as general...
> The initlal reason we used LXD's logger was to avoid reimplementing one for each LXD-adjacent project. All the micro-apps were designed with LXD in mind, so using the same...
@roosterfish @skozina shall we close this or move it to microcluster repo? I believe the plan is to move to Go's built in slog and not depend on LXD's logger...
I'd be tempted to make this a property of the `disk` device that attaches the volume to an instance, rather than a property of the volume itself, as that then...
Something related recently landed in Incus https://github.com/lxc/incus/pull/1415 Thinking about this more the uid/gid maybe able to be device specific (if we consider idmapped mounts) however the permission of the volume...
@jonathan-conder this PR from Incus may also help the situation: https://github.com/lxc/incus/pull/1092 It allows to mount a sub-directory from a custom volume as a disk in the instance.
Hi, Do you still experience this issue using latest/stable (5.21.1) as LXD 5.20 isn't supported anymore?
Hi @MaxRower apologies ive not had chance to investigate this yet
@boltmark please can you look into this when you get a chance. Thanks!