How to troubleshoot Workshop

If you notice issues with workshops, projects, or Workshop in general, it may be time to verify or update the installation or prerequisites.

Check and update version

Ensure your version matches the latest release on GitHub:

$ snap info workshop

  ...
  installed:    0.1.13 (x18) 24MB classic

If it’s outdated, upgrade the installation: Upgrade instructions.

Install and start LXD

A major prerequisite for Workshop is LXD; ensure it’s installed and running:

$ sudo snap install --channel=6/stable lxd
$ sudo snap start --enable lxd.daemon
$ sudo snap services lxd

You may need to add yourself to the lxd group to access its resources:

$ sudo usermod -a -G lxd $USER

As a final step, see the troubleshooting guides in LXD documentation.

Check the snap logs

Before resorting to the debugging guide for individual workshops, review the snap’s logs:

$ sudo snap logs workshop

Explore LXD containers

If you notice an issue with a specific workshop, use the LXC utility to identify and troubleshoot it.

For instance, if you’ve deleted a project without first removing the associated workshops, you can list all LXD projects to locate the orphaned containers. These will appear under workshop.<USER> and include the Workshop project ID in their names:

$ sudo lxc list --all-projects

  ...
  | workshop.user | nimble-ec275767 | STOPPED | | | CONTAINER | 0 |

Next, you can manually delete a container:

$ sudo lxc delete nimble-ec275767 --project workshop.user

Or, you can shell into the container to recover its data:

$ sudo lxc shell nimble-ec275767 --project workshop.user

If the container fails to start, use lxc info to view the latest log entries:

$ sudo lxc info --show-log nimble-ec275767 --project workshop.user

To increase log verbosity, you can reconfigure LXD with snap:

$ sudo snap set lxd daemon.debug=true
$ sudo snap restart lxd.daemon

Use other relevant LXC commands to continue your investigation.

See also

How-to guides:

• How to debug issues in workshops