I'm familiar with Proxmox, but it doesn't natively support docker.
I'm familiar with Proxmox, but it doesn't natively support docker.
It was originally developed as an absolute minimal distro for running containers on servers, but the immutable desktop movement led them to develop a desktop user-facing variant.
Other ideas that are very similar: Fedora SilverBlue (very similar, more mature) and VanillaOS (based on Flatpak insteak of Podman/Docker, very new)
> OpenSUSE MicroOS has a read-only root file system, using Btrfs. Transactional updates are handled by a SUSE-specific wrapper script around the package manager zypper, transactional-update. This creates a new Btrfs snapshot of the root file system and then performs an update of the system. If the installation was successful, the script marks the new snapshot as the default snapshot. On errors, the snapshot is discarded and the previous one remains as the default. A reboot activates the new snapshot.
My comment above was saying that you don't have to use MicroOS per se to get this. A regular openSUSE install supports the transactional server role that does the same thing as MicroOS.
The idea and execution is very similar to MicroOS, both on the desktop and on the server. Immutability isn't as scary as it sounds, highly recommend checking it out.
No webgui though, that has to come from another project...
https://rancher.com/docs/os/v1.x/en/support/
Rancher is working on a new version.
All of this left me feeling like the devs had different goals than I did as a user.
But the current iteration seems like k8s/helm are first-class features now, so yeah, should definitely look again.
[1]: https://github.com/linuxkit/linuxkit/blob/master/ADOPTERS.md
Its almost certainly the most performant distro in this huge thread (unless your host is ARM).
But I've never quite understood the appeal. Is it about running untrusted containers with VM-level isolation? Or having a familiar GUI for managing and lifecycling them? Something else?
Fundamentally, I worry that mixing VMs and containers is more likely to end up with the worst of both worlds rather than the best— basically you get the slow bootup of starting the kernel every time, but none of the application-level benefits of sharing base layer storage or mounting the same shared volume to multiple containers at once.
Relatively long-lived, potentially multi-process server things is what LXC is for. It makes more sense to run LXC than Docker in that situation anyway. -_-
Although personally, I prefer Podman over Docker.
Proxmox is neat and you can run any OS under the hood including the suggestions mentioned.
You could also go for NixOS and declare you need OCI (e.g. Docker or Podman) in your Nix config.
https://www.truenas.com/docs/scale/scaletutorials/apps/docke...
https://www.virtualmin.com/documentation/cloudmin/virtualiza...
Is this a server? CoreOS
Portainer or Cockpit for web UI
Or Fedora Kinoite! IMO KDE is probably a better fit for the root commenter's "I just want a UI" position.
I’m sure it’s actually very straightforward and I’m just an idiot, but I haven’t had much luck.
We found that even with a web GUI, containers are just too complicated for the typical user "that knows nothing about containers".
Even with a GUI, no matter how nice it is, you need to learn about env vars, port mappings, cni networks, bridging, volume mounts, images, tags, host isolation, etc etc..
Our solution is to wrap apps into pre-packaged recipes. Pretty big trade-off of course, but it makes the installation and management completely fool-proof afterwards.
You can see some screen shots in the documentation here:
https://sentinelc.com/docs/user-guides/administration/manage...