About me
I am a senior linux and network engineer with 12 years of experience in IT. A bit of an all-rounder with a focus on infrastructure, (Ubuntu) Linux and Kubernetes.
Over the past several years, I have been an active contributor to the Canonical LXD ecosystem, for both the LXD daemon itself and the LXD-UI web interface. I actively triage, report reproducible edge-case bugs, propose UX/feature improvements, and submit code/documentation fixes to help strengthen Ubuntu’s native system container and VM platform.
Contact information
Launchpad: Daniël Vos in Launchpad
Github: vosdev (Daniël Vos) · GitHub
Contributions
My contributions to the Ubuntu ecosystem center primarily on the LXD and LXD-UI projects through code contributions, detailed bug reports, feature requests and design feedback, and documentation.
With over 200 contributions to LXD and LXD-UI alone, I cannot go into detail for every contribution. Instead, I will highlight some contributions.
At the moment of writing, 131 out of 344 issues reported to canonical/lxd-ui are created by me: Issues · canonical/lxd-ui · GitHub
For the main LXD project I am also responsible for a total of 73 issues: Issues · canonical/lxd · GitHub
Merged Pull Requests:
- canonical/lxd-ui#2105: Making instance configuration mobile-friendly for the LXD UI
- canonical/lxd-ui#2106: Making the image selector responsive for the LXD UI
- canonical/lxd-ui#2212: Add the ability to configure user.keys via the UI
- canonical/lxd-ui#2239: Prioritize main interfaces on sorting
- canonical/lxd#18836: Add documentation on how to set up SSO for LXD with authentik
A few highlighted recent critical issues:
- canonical/lxd-ui#2159: Memory leak and 100% cpu usage on network disconnect - Diagnosed root cause and provided detailed reproduction steps.
- canonical/lxd#18873: Broken OIDC token refresh - A fix was introduced very shortly because of the detailed information I provided, with the maintainer thanking me in the PR.
- canonical/lxd#18727: Infinite loop causing 100% CPU usage - resolved within a few hours because of the detailed debugging information
- canonical/lxd#16652: Wrong values cause a destruction of the network configuration - Close cooperation with multiple developers to help quickly solve this destructive bug.
Advocacy
I am a LXD/MicroCloud advocate on reddit in r/sysadmin, r/homelab and r/selfhosted
Future goals
I am a big fan of the LXD project and my contributions will continue on as they have for the past few years.
I also have plans to start my own blog where I will write guides for setting up LXD and MicroCloud in several ways. These will be shared on the Ubuntu Discourse in the LXD Tutorials section.
Testimonials
If you have worked with me or interacted with my contributions across LXD, LXD-UI, or the wider community, your endorsement below would be greatly appreciated ![]()