Containers really shine in the selfhosting world in modern times. Complete userspace isolation, basically no worries about dependencies or conflicts since it's all internally shipped and pre-configured, easy port mapping, immutable "system" files and volume mounting for persistent data... And much more. If built properly, container images solve almost all problems you're grappling with.

I can't imagine ever building another application myself without containerization ever again. I can't remember the last time I installed any kind of server-side software directly on a host without containerization, with the exception of packages required by the host that are unavoidable to support containers or to increase security posture.

I'm my (admittedly strong) opinion, it's absolute madness, and dare I say, reckless and incomprehensible, why anybody would ever create a brand new product that doesn't ship via container images in this day and age, if you have the required knowledge to make it happen, or the capacity to get up to speed to learn how to make it happen (properly and following best practices of course) in time to meet a deadline.

I'm sure some would disagree or have special use-cases they could cite where containers wouldn't be a good fit for a product or solution, but I'm pretty confident that those would be really niche cases that would apply to barely anyone.

While php is still cool... join the dark side and start using containers 😏

And that's why my rule is: if it doesn't container it doesn't go on my server. If I can't get the application crammed into my docker compose stack I look for an alternative. Hell I run PiHole and Octoprint inside container

[This comment has been deleted by an automated system]

retvrn to cgi-bin

The thing that boils my blood is secret sqlite databases. I just want to store my volumes on an NAS using NFS, and run the stacks on a server built for it. Having a container randomly blows up because an undocumented sqlite database failed to get a lock sucks ass.

Sometimes venting off a little helps a a little. I finally sat down and learned the basics of docker and found an easy to follow video series on how to setup Docker with Portainer and Nginx Proxy Manager. Works like charm. I also set up my GoToSocial instance again but failed at setting up a Lemmy instance … but I guess that’s for another discussion :)

I recently(ish) installed Unraid on a new NAS, as I’d heard good things but knew nothing about it. Didn’t really intend to install much on it, but got playing around with the Docker stuff built into it and... fuck me. The amount of time I used to spend installing dependancies, configuring stuff, trying to work out why the hell it wasn’t working. With really not much work I’ve got a fully fledged Arr setup with Jellyfin, got a full dev environment, Grafana and influx for monitoring, automated tls certs, and a bunch of other things all working pretty damn flawlessly.

Containers are awesome.

Docker containers do pretty much solve that, drop a docker-compose.yml file in place, maybe tweak a few lines, and that's all.

Not sure what's the problem though. Pull up a reverse proxy, and give all the crappy shit a private ip and whatever port they want, and access it through the proxy, and everyone can be on 443. 127.42.1.123:443, whatever. Maybe use real containers, or that crappy docker shit, both offer you independent namespaces with all the port and whatnot.