LXD Reviews & Insights

Creating local deployments of complex projects for development and testing purposes. It's mostly used by developers to replicate a production environment in their local machine, but it's easier to set up than a Virtual Machine. Although I've used Linux Containers LXD in one project in the last few years it's made almost obsolete by more modern projects like Docker, which enable you to do the same thing with a more organized approach that can be easily shared with other developers and quickly spun up in development or even production machines.

Linux Containers LXD works very well when you, as a software developer using Linux, need to spin up a development environment to build and work on a specific piece of software. For example, you need to build some software that is tested and developed target Ubuntu 18.04. You're able to quickly create a container for Ubuntu 18.04 and log into it to run commands and build your software. This is easier to do than setting a virtual machine - e.g - via Virtual Box, but is a lot clunkier than doing it via Docker containers which give you a much more flexible configuration of the environment and are easier to start, stop, connect and share with other developers.

Linux containers ease our deploys - you can do it in a few command lines and the ability to access the server from the host shell with no issues and save some time in order to release a server 'cause you can create a standard image and to rollback anything if needed.

Scenarios where you need an authentication server, a GIT repository the system works very well 'cause you don't need any scalability and the ease to configure and share the same Linux system image across the containers and the rollback process is quick. I didn't put any critical applications there not because of the limitations but due to a company policy.