Lennart Sorensen <[email protected]> wrote: > Certainly as far as I have understood it, kubernetes manages docker > containers,
Kubernetes orchestrates Docker [packaging] ... is more of the term. But Kubernetes can use Podman [packaging] and tooling too. so given how popular kubernetes seems to be, docker isn't > going away. docker swarms and other management bits that docker inc > has on the other hand seem to be dying out. Perhaps this is why the > docker engine is now named docker-moby rather than just docker to try > and avoid the confusion a bit. Not sure it is working. > Moby is the Upstream project now, which is a bit of an over-simplification. Red Hat is not helping things by putting non-Podman et al. in the 'Extras' channel, which means they make no guarantees of non-breakage in updates -- like what happened to use with RHEL7.7. RHEL8 enables CGroups v2 by default, which means Moby doesn't work by default, so isn't installed by default. But the poster here was talking about Proxmox ... Again ... no one has still explained the Proxmox components to me, and every time I get a few minutes to look at the architecture-code, I see a lot of copyright and Upstream that isn't theirs. I honestly wish I had enterprise experience with Proxmox, but it's hardly the only FLOSS out there, let alone relies on so much Upstream. I.e., it's not the only thing 'fighting' VMware's ecosystem based on mid-sized (1-5K instance) environments that were 90% Windows just 10 years ago, but becoming >>50% RHEL (like my current, mid-sized employer). Professional Experience: I've been 'fighting' VMware since oVirt (RH[E]V) and Origin (OpenShift) became available at the start of this decade. And they know who I am for that reason, especially when I was publicly critical of their 'joke' of an API in Perl back in '08-09, and was attempting to automating all sorts of crap. As IBM put it to me very well in FSI, "VMware doesn't care, they don't see it as something they should care about, they make a lot on the Windows ecosphere and selling their professional services and 'point'n click' job security for its users." Well, I was one of the people that made them care with some massive wins, including an 8 figure one (that cost them the potential 9 figures of their money). So, if anyone wants to take this off-list, I'm all ears. I want to understand Proxmox architecture and code better than I have been exposed to. Enterprise experience is key for me, and I don't like to assume from just reading things, especially automating and orchestrating a lot with other tooling the past, full decade-plus -- both VM and pre-LXC 'cartridges/gears' (i.e., early OpenShift 'pods,' if you will). - bjs >
_______________________________________________ lpi-examdev mailing list [email protected] https://list.lpi.org/mailman/listinfo/lpi-examdev
