LXD container instances are much better suited for portable dev environments. They are persistent by default and are intended to run multiple processes within a container instance. They can also be copied/migrated between lxd agents.
In contrast, docker was created to run a single ephemeral process per container. It's nice in production environments, but its also a huge pain for some tasks. That's why were seeing folks create things like docker s6-overlay.
Thanks for the suggestion, this looks great! At a glance LXD seems to be a much more robust version of what I've built. Time to learn something new I guess lol.
Yeah there’s the downside. The interface is a bit unwieldy. Documentation for lxd is far lower quality compared to the massive and mature docker ecosystem.
However if you know a lot about what docker does at a lower level, that knowledge is transferable to something like lxd. Most of these containerization tools are all using the same Linux kernel features under the hood!
LXD container instances are much better suited for portable dev environments. They are persistent by default and are intended to run multiple processes within a container instance. They can also be copied/migrated between lxd agents.
In contrast, docker was created to run a single ephemeral process per container. It's nice in production environments, but its also a huge pain for some tasks. That's why were seeing folks create things like docker s6-overlay.