Yep, some people sort of miss the point of microservices and make some fairly monolithic containers. Or they’re legacy apps being shoehorned into a container. Some things still require handholding. FreeIPA is a good example. They have a container version, but it’s just a monolithic install in a container and only recommended for testing.
Containerfiles are super easy to write. For the most part if you can do it in a VM, you can do it in a container. This sort of thing is why you would move to containers. Instead of being the “expert” in all the apps you run, you can focus on the things that actually need your attention.
I literally get paid to do this type of work and there is no way for me to be an expert in all the services that our platform runs. Again, that’s kind of the point. Let the person who writes the container be the expert. I’ll provide the platform, the maintenance, upgrades, etc… the developer can provide the expertise in their app.
Correct, not all containers are for services. I would never say that docker is superior. I would however say that containers are (I can be pedantic too). They’re version-controlled, they come with the correct dependencies, etc… There are many reasons why developing with containers is superior and I’m sure you’re aware of them already. Everyone is moving to do exactly that. There are always edge cases, but those are few and far between these days.
30, that’s cute. I currently have 70 containers running on my home server. That doesn’t include any lab I run or the stuff I use at work. Containers make life much easier. I also guarantee you don’t know those apps as well as you think you do either. Just being able to install and configure something doesn’t mean you know the inner workings of them. I used to do the same thing you do. Eventually, I would rather spend my time doing other things or learning certain things more in-depth and be okay with a working knowledge of others. It can be fun and rewarding to do things the hard way but don’t kid yourself and think you’re somehow superior for doing it that way.
Well, yes that’s best practice. That doesn’t mean you have to do it that way.
You absolutely can. It’s not like the developers of postgresql maintain a version of postgresql that only allows one db. You can connect to that db and add however many things you want to it.
That’s half the point of the container… You let an expert set it up so you don’t have to know it on that level. You can manage fast more containers this way.
What? No it doesn’t… You could still have just one postgresql database if you wanted just one. It is a big antithetical to microservices, but there is no reason you can do it.
Ha, that would be excellent. Don’t forget Sony and PlayStation.
Canonical is mostly a leech on open source.
Sure, that’s why they keep adding features people don’t want. But gimping one of their key paid features makes no sense to me.
Every update they’ve made for just about the past decade has made the product worse for the original users who just want to stream their own media. This last UI update killed my favorite download feature. They deserve the hate they’re getting.
The update makes the download feature objectively worse. So, that was a stretch to praise both.
They seriously enshitified the download feature. You used to be able to set it to download X number of unplayed episodes. Then it would manage downloading fresh content for you as you watched stuff. Now you have to manually download each and every episode yourself. This was literally the killer feature Plex had over Jellyfin for me.
Broadcom is doing an excellent job convincing their customers to stop using VMware. Such a good job that at Red Hat we’ve shifted strategies with OpenShift Virtualization to pick up those customers. For the longest time our Virt play was just a stop gap to containers, now it’s a full blown product.
On one hand, there is a lot of potential to use solar power. On the other hand, cooling that isn’t going to be a bitch.