S家的container

cyberwillis

Yeah there is a learning curve to use containers, but the benefit is the speed and isolation between every application (one don't interfere into another),
Example: If you use a release from 2019 and another release from 2025 they may need different OS with different libraries resources, the benefit is because the applications become isolated from each other in a vessel (container) that only have the basic libraries the application need to run and all the kernel is inherited from your Host Machine (be Ubuntu, be Fedora, be Kali, etc) running at 95.9+ % speed of the Host machine almost no latency.
Another point is the Host machine can run the License Manager and each container (running a specific application) connect to the license server individually consuming only the license required (by a private network). However the code that build their  container may have undesired services. . I would prefer build the container myself.

BTW thanks for the PDF!!!

难受至极

cyberwillis 发表于 2025-5-20 06:55
Yeah there is a learning curve to use containers, but the benefit is the speed and isolation between ...

大体上懂了，感谢各位

cyberwillis

gotoibm

What's the difference between S' container, docker and Vmware/virtualbox vm?

cyberwillis

gotoibm 发表于 2025-5-26 15:53
What's the difference between S' container, docker and Vmware/virtualbox vm?

In Docker Container or any other kind of container it doesn't have a kernel to be emulated. It uses the Kernell of the machine you have and use a small file system structure only with the files and libraries necessary to the application you will run.In other words is not a fully Operational System. The performance loss is about 1% - 5%  compared to the application be installed direct to the Host machine.
In a Virtual Machine the loss in performance can be significant bigger because the Virtual Machine Hypervisor needs to emulate the kernel because is a full operational system installed inside with many services. The loss can be around 25% - 50% in some cases.

Think about it, one container for just the application you need and all of them can run in parallel as you have more memory and resources as if was isolated from each other without having libraries conflicts between year versions or even GLIBC requirements.

If one app requires a Rock8 you can just put it there and start it.
If another app requires Rock9 / Centos9 you can just put it there and start.
If another app requires a Centos5 and your Host OS doesn't works anymore with old libraries you can just launch a container of a old OS and put the app inside it and use it without needing to look for the possibility of a new version being released.
Also two or more containers can share a specific internal network or a common "shared folder" mapping inside the host in order to make easy to pass files between them.