>>108515888
Nice trips.
This ship is painful on windows I had to reboot billions of times just to get it to work.

>>108515897
I have my instances running on WSL2. It's worked pretty well but if you try to run Docker as a service it makes it so you can't get back into Docker Desktop unless you reboot with the startup service disabled.

Probably should learn how to just do things from the CLI.

>>108515888
Unless you own nothing but a laptop and are being happy about it rn, you should try proxmox if you want to see convinience.

>>108515888
yeah docker containers are nice but docker itself is full bloat, I switched to podman on my personal machine and projects, a bit lighter and you can use docker and docker compose too.

>>108515888
Docker blows
Kubernetes is better

>>108515946
Podman is the globohomo version of docker.
The new versions have a hard dependency on netavark and aardvark which are written in Rust and depend on systemd.
Not even once.

>>108515938
Single Proxmox instances are manageable, clusters are painful to manage. I would recommend against using Proxmox for larger deployments.

>>108515950
KEK

>>108515946
OrbStack rules.

>>108515966
Do you seriously believe Docker *isn't* globohomo?

>>108515950
no?
k8s is fine if you need multiple replicas, autoscaling, other blah blah corporate requires
for selfhosting - docker is plenty

>>108515950
They're not really competing since docker swarm died

>>108515888
It honestly makes it brainless, especially with compose.
Just pull the repo, docker compose up -d and you're off the races.

>>108515888
>>108515938
I have a single Proxmox server with ~5 Ubuntu VMs that serve multiple purposes. Unifi controller, Plex, etc.. These VMs barely take up 1% of the CPU I allocate to them, and I set a minimum of 2 GB Balooned to 8 GB. The resource demand is so low. Why should I consider docker? Would an alternative deployment be setting up a Ubuntu VM and installing docker on that, and then deploying my services that way?

>>108516540
I just do an LXC container running Debian and put docker on that.
And no I don't give a shit what nerds say about whether or nor its a good idea to run docker in an LXC. It works great for me.
The reason I like this setup is I can abstract the software away from the system, and then I can further abstract my versioning so I get snapshots. That way, if I somehow ever fuck something up at the configuration level I can just roll back via Proxmox backup. They're pretty small for LXCs. For example, my SearXNG LXC is 700 mb per backup.

>>108515897
why would you use docker on windows

>>108516198
Docker is Globohomo Lite
Podman is Globohomo Max

>>108516641
I guess docker containers save resources so you don't have to spin up multiple VMs per service like I do, and you can maintain separation of services instead of installing everything on a single VM like a retard.

>>108516670
I put a Docker instance into a VM to run a single server but that was more for routing purposes (I didn't want to route the port that connected to that server to my host server's IP, I wanted a standalone IP I could forward to).

>>108516670
That too, I separate most of my services by what I'm trying to accomplish. I do run Portainer in a single LXC, for instance, but everything on it is related to the *arrs, ombi, qbittorrent, and sabnzbd.
Everything else gets their own LXC/vm so I can separate services, mounts, etc. That also means that from backup to backup I know exactly what should be inside.

I just use lxc with a few shell scripts to set up a new tainer
too lazy to learn whatever the hell docker does

>>108515888
what kind of container orchestration would you recommend for a singular small team? k8s seems overkill

>>108517214
I would just use Portainer.

>>108517214
simples and what i use - dockge
used to use portainer, but I like having my compose files stored nicely in folders
if you need role based access control and more features in general - komodo is great
tried using, felt nice, but way overkill for my needs