lxd-dashboard VS watchtower

LXD Dashboard for easy managing lxc https://lxdware.com

The Ararat project lacks screenshots or any detail, so I can't quite say what direction it's heading as compared to the other several LXD-specific dashboards/control panels out there (lxdware, LxdMosaic and others).

https://lxdware.com/ https://github.com/lxdware/lxd-dashboard or the older https://github.com/AdaptiveScale/lxdui.

In that case, let's throw caution to the wind! Ubuntu (debian-based) + lxd (manages lxc containers and qemu VM) + an lxd webUI (https://github.com/turtle0x1/LxdMosaic or https://github.com/lxdware/lxd-dashboard). Unconventional option as lxd usually flies under the radar, but it is a nice alternative to proxmox.

+1, but there are two community webUIs for LXD: https://github.com/lxdware/lxd-dashboard and https://github.com/turtle0x1/LxdMosaic

You won't have a single webUI to manage everything. But LXD has a couple different webUIs to manage those containers and VMs: https://lxdware.com/ and https://github.com/turtle0x1/LxdMosaic

Here two examples. I personally used the first one in the past and it was great. (now I just don't have lxc containers anymore). https://lxdware.com/ https://github.com/turtle0x1/LxdMosaic

Related: https://github.com/containrrr/watchtower

> if you're using the docker image, upgrades are a breeze. Just bump the tag on the image, redeploy, and you're done.

Or you could just run Watchtower beside it and it will automatically update your docker containers. https://github.com/containrrr/watchtower If you are OK with automated updates.

So i primarily use containers on my local machine walled off from the internet, so it's not a big concern for me. Watchtower [1] is popular among home server users too which automatically updates containers to the latest image.

For production uses I think companies generally build their own containers. They would have a common base linux container and build the other containers based off that with a typical CI/CD pipeline. So if glibc is patched, it's probably patched in the base container and the others are then rebuilt. You don't have to patch each container individually, just the base. Production also minimizes the scope of containers with nothing installed except what's necessary so they have few dependencies.

[1] https://github.com/containrrr/watchtower

You can use Watchtower (https://containrrr.dev/watchtower/) that solves problem of manual pulling on VPS.

I checked https://containrrr.dev/watchtower/ and Arguments, but I don't understand where to attach that using portainer.

Again, there are options to automate some of the burden here by using tools such as Watchtower.

Have you ever deployed a Docker app on a server, but everytime you push a new version of your image to a Docker registry you need to manually restart your app? If you want to automate this restarting, this blog post is for you! I am now going to show you how you can do this with literally 1 simple command using Watchtower!