2 ms·
Generally even in containerized deployments, you run one container per service/process. You wouldn't run everything you’d run on one box in one container. I d
by sneak 2y ago
Generally even in containerized deployments, you run one container per service/process. You wouldn't run everything you’d run on one box in one container.
I definitely recommend using docker compose or similar even in a one node deployment versus just installing and running things on the host linux system like it’s still 1998. Having a single directory to back up and a single file defining all of the services that can easily be redeployed is very convenient.
- RandomThoughts3 2y agoThe performance impact seems completely unjustified for most of the things people do with a personal machine however.
- consumer451 2y agoWhat is the performance impact? Going one page into Google results, I found this paper. Is there a better reference? > At light workload levels, the native host performs better than Docker. However, as the workload increases, both Docker and the native host show similar performance, with the difference getting smaller https://www.researchgate.net/publication/376557310_Comparative_Analysis_of_Apache_2_Performance_in_Docker_Containers_vs_Native_Environment https://www.researchgate.net/publication/376557310_Comparati...
- RandomThoughts3 2y ago> What is the performance impact? DNAT, layered file system access, likely duplication of libraries if you don't pay much attention to your containers.
- sneak 2y agoThe performance impact is approximately zero.