Hmm docker is resource isolation not a VM. Strange unless running it on windows or Mac or something cross architecture

It's not docker itself. It's the mindset of some of its users: just throw in every garbage and don't bother about maintenance.

It's also often used by users shying away from maintenance -- often due to a demanding schedule. Sometimes not grasping the level of investment they need to do to have a good Dockerfile. If seen too many self-managed installations where the user mapping is utter crap an the process are running with random system users or random end-user UIDs.

If you have to do may round-trips to display a page after a UI action, and most round-trips involve hitting the storage on the server, the UI will feel slow sometimes.

Nextcloud isn't lighter and leaner outside of docker. It isn't faster either

On the other side, docker is just installation system, so why even care.

100%. This person is a very specific anti-* hater, for something that was such a rampantly popular hatred 10 years ago. But the FUDites rarely bother with bona-fides, with real argument.

We should feel bad for them, those decoupled folks who needs help. It's sad pathetic and remarkable how these weird software enmities crop up, are let to grow and never addressed. Their time of their outrage being popular & hip fades but the disdain-without-argument sticks around.

Thankfully container hatred is a pretty tiny frakking force, of very disparate widely scattered eccentrics these days. But there's so many weird FUD proclivities folks can opt into, can find to stoke their lifelong hatreds against. Theres just so few warnings: such audience acuity is required to parse, realize the windmill tilting, & move along.

You wouldn’t deploy NextCloud if not for docker.

Strange, on my nixos seems to be possibel!

I actually manually ran both ownCloud and Nextcloud manually before switching to docker.

Edit: just checked because I remember upgrading to Owncloud 6... This was 12 years ago to be fair.

Docker makes things slow now? What?

I understood that their point was not that Docker makes it slow, but that if it needs Docker to run, it probably needs a complicated environment which makes it slow.

Which makes it an inaccurate and incorrect point.

I’m not using docker to deploy things because the things I’m deploying need a complicated environment, I’m using it because it’s an incredibly easy and consistent way to deploy things. It’s an immutable image that is highly convenient to distribute, update, and manage, which is pretty much the opposite experience of installing software on virtual machines.

Dropping a docker compose file into Portainer and I’m up and running with a new service in a few seconds. I’ve removed the overhead and spin up time of VMs, there’s no more running Chef/Ansible to do basic VM management for every single service I’m running, no more cookbooks/playbooks or manual SSHing to get software updated, no more minutes to hours of fixing configuration management that never seems to work the first time, no more bad in-place upgrade states, etc.

> it’s an incredibly easy and consistent way to deploy things

I keep seeing people saying this but my experience has always been otherwise.

Docker makes it really difficult to tinker with the internals of the container. They call it a development environment but you can’t easily edit a file and restart a service. There is bind mounts but the IO performance is terrible, necessitating use of volumes. Every base image is opinionated in how things are done, where things are stored even for the same software.

Since it’s so difficult to tinker with the internals most vendors will provide a web interface abstraction on top of their software (like NPM for nginx) and if you so much so veer off the happy path by 1 inch the abstraction can no longer track the state of things and breaks, necessitating a full reinstall or editing the config manually.

Of course this is in the context of self hosting. If you’re paid in your day job to maintain a tower of babel then by all means fire up all those dynos.

I don’t think of it as a “development environment” so much as a “deployment environment.” Yes, it is more difficult to “tinker” with a running container. And for services that are just supposed to run and not be tinkered with, that’s wonderful. I’ve deployed services that run on literally tens of thousands of containers and needing to tinker with the innards at this point is kind of a smell, like if you said “yeah, but I need to be able to add oil to my car while driving down the street because you never know when it’s all gonna suddenly leak out,”

Also, wasn’t this comment about perf?

Why do I need to tinker with the internals of the container?

Even if I need to do that, the existence of a Docker image doesn’t stop me from making my own implementation as long as the application in question provides some kind of alternate distribution.

E.g., if there’s an RPM/DEB package, binary executable, JAR file, source code, etc, I can just make my own docker container with my own implementation and mess around with the internals as much as I want.