Azure Container Service vs LXD: What are the differences?
Azure Container Service: Deploy and manage containers using the tools you choose. Azure Container Service optimizes the configuration of popular open source tools and technologies specifically for Azure. You get an open solution that offers portability for both your containers and your application configuration. You select the size, the number of hosts, and choice of orchestrator tools, and Container Service handles everything else; LXD: Daemon based on liblxc offering a REST API to manage containers. LXD isn't a rewrite of LXC, in fact it's building on top of LXC to provide a new, better user experience. Under the hood, LXD uses LXC through liblxc and its Go binding to create and manage the containers. It's basically an alternative to LXC's tools and distribution template system with the added features that come from being controllable over the network.
Azure Container Service and LXD are primarily classified as "Containers as a Service" and "Virtual Machine Platforms & Containers" tools respectively.
"Easy to setup, very agnostic" is the primary reason why developers consider Azure Container Service over the competitors, whereas "More simple" was stated as the key factor in picking LXD.
LXD is an open source tool with 2.28K GitHub stars and 531 GitHub forks. Here's a link to LXD's open source repository on GitHub.