Repository navigation
Identify LXD errors transparently, or provide some other support for recovery #1121
Description
When LXD is not working properly, workshop seems to be forwarding the LXD error, but without identifying LXD as the source, or providing a trace or hint at log files, or hints at solving the problem.
In this case, sudo snap restart lxd did the job, but as I don't know what didn't work, hard to tell...
◎ workshop launch
error: system is not healthy: Failed beginning transaction: cannot rollback - no transaction is active
○ workshop list
error: system is not healthy: decode rows: unexpected type 6
Metadata
Metadata
Assignees
Labels
No labels
Activity
jonathan-conder commentedon Nov 3, 2026
These are certainly quite cryptic. We should be indicating where they come from.
I think we should reserve hints for the most common errors we see from LXD, it's not really feasible to anticipate every possible error on our side. But I think we should ask LXD to improve these two messages if you haven't already.