4 ms·
Unpacking Linux containers: understanding Docker and its alternatives
- ottoke 3y agoMost devs use #Docker or #Podman, but do you really understand what’s happening under the hood? Let’s demystify #Linux #containers in simple, concrete terms. Just a 12-min read!
- sneed_chucker 3y agoThis is not a hashtag website.
- MrDrMcCoy 3y agoSadly, no mention of ststemd-nspawn. Image management is manual, but it's otherwise a very powerful alternative.
- mistrial9 3y agoDocker is back-doored by design.. false?
- zackees 3y ago[dead]
- simonblack 3y agoIs it true that Docker is single-threaded (or only allows a single thread)? I had a guy who ran some of my software once that said it wouldn't work in Docker. My software used several threads. I'm sure that I read somewhere that one of the problems with Docker was that it only allowed single-threaded programs to work.
- kuhsaft 3y agoThat is false. Creation of threads/processes is still available within a container. Docker will run the entry point as PID 0 and that process can create as many subprocesses as it wants. If you’re talking about cores, Docker utilizes Linux cgroups which permits usage of multiple cores. You can limit the CPU quota and assign the container to specific cores. See https://docs.docker.com/config/containers/resource_constraints/#cpu https://docs.docker.com/config/containers/resource_constrain...
- pjmlp 3y agoBesides FreeBSD jails, there was AIX Workload Partitions, Solaris Zones and HP-UX Vaults.
- vermaden 3y ago... and they ALL were (and still are) in production long time before Docker went viral.