Luciano Lo Giudice

Sorry about the confusion. I mean these: https://github.com/canonical/lxd/tree/main/shared/logger

Yes, of course. The [microceph](https://github.com/canonical/microceph) project currently leverages LXD libraries to simplify deployment and make use of a comprehensive code base. One issue we've seen in embedded deployments is the...

> @masnax @lmlg perhaps micro* repositories should switch to using slog from Go https://go.dev/blog/slog I personally don't think a library switch is needed. In our case, it would suffice to...

> So I'm generally against this change due to opportunities for regressions and 'papering' over the bug. Essentially charm-helpers 'owns' the file `.unit-state.db` as it predates the ops framework, and...

just to get this right - You used `log set-level` to something more suitable, and still it appears that the log level is set at `DEBUG`? If so, we'll need...

Getting an `EPERM` error from `pthread_create` leads me to think that this is an issue with the running environment and Go's runtime - essentially, this can only happen when creating...

Sorry about the confusion. I mean these: https://github.com/canonical/lxd/tree/main/shared/logger

Yes, of course. The [microceph](https://github.com/canonical/microceph) project currently leverages LXD libraries to simplify deployment and make use of a comprehensive code base. One issue we've seen in embedded deployments is the...

> @masnax @lmlg perhaps micro* repositories should switch to using slog from Go https://go.dev/blog/slog I personally don't think a library switch is needed. In our case, it would suffice to...

there appears to be an issue when building the snap related to the lxd user/group and permissions.