🇳🇱
@magicaltrout What do you mean by "full init chain"?
@freemo like running systemd services or whatever, multiprocess stuff like a more traditional vm as opposed to dockers more general 1 running process mode of operation
@freemo Have you used Proxmox? It's the equivalent of Portainer, essentially. Very comfy to work with, especially when you need to run software that has no easy way of running in docker, or just a host that has more stuff in it, but not necessarily enough to be a full-blown stack of services with docker containers. And for fun, obviously
@state Ive used portainer but not proxmox.
@freemo I'm using it. From a technical point of view, it seems to me a very robust technology, but from a philosophical point of view, if you are serious at DevOps, probably there are better solutions.
If you have some legacy service that had to run inside a normal Linux distribution, then LXD allows to create a guest distro that is very light, because behind the hood it runs as a Linux container of the host distro. So you have a very cheap distro to use for: testing porpouses; local and disposable environments to give to students; legacy services administered in the old way.
Obviously if a service is important and it requires some resources, it is better to install on a distinct VM, instead of using LXD.
A modern DevOp environment, built from scratch, I doubt that it should follow the LXD approach. It is mainly for services that for some reasons are managed in the old way, and it does not make sense to host on distinct VMs. So a very narrow use case.
whats the reason most people use lxd or docker? to run a #web #app?
whats the "time-to-#http-#response" for #lxd?
tthr???
i made it up..it means the time it takes to install a application that reacts to your #http #request from your public http request.
for #docker-compose + #wordpress + #tor its 46 seconds !
@freemo I used to use LXC/LXD back in the day, if you have a need for a full init chain or similar, there's a use case, but otherwise, there's enough differrent ways that are more common to separate workloads.