Teknikal_Domain on Nostr: npub1l3gpk…qvu48 This is why stacks and docker-compose exist. You give it a YAML ...
npub1l3gpk6vrudg8r67swqlex5alv9ch59s4lw46kk6hekuxe2n3aczsyqvu48 (npub1l3g…vu48)
This is why stacks and docker-compose exist. You give it a YAML file detailing what containers, what images, what networking, what <everything> configuration, and tell it to start that, and it handles organizing the containers for you.. and if you set it up right, I think that even has some scalability too.
But this is why I say a Docker container is not a VM-lite, it's an app in a sandbox. Compared to what I'm normally using, LXC containers, which *are* meant to act as a full Linux system, Docker containers are meant to just draw boundaries around a single process in regards to it's filesystem access, environment, and maybe memory and CPU.
npub1trdnqrfstufc45awha43p6xy2n0v6czuhapzh4r09hap08dg0c6s9gussx (npub1trd…ussx)
This is why stacks and docker-compose exist. You give it a YAML file detailing what containers, what images, what networking, what <everything> configuration, and tell it to start that, and it handles organizing the containers for you.. and if you set it up right, I think that even has some scalability too.
But this is why I say a Docker container is not a VM-lite, it's an app in a sandbox. Compared to what I'm normally using, LXC containers, which *are* meant to act as a full Linux system, Docker containers are meant to just draw boundaries around a single process in regards to it's filesystem access, environment, and maybe memory and CPU.
npub1trdnqrfstufc45awha43p6xy2n0v6czuhapzh4r09hap08dg0c6s9gussx (npub1trd…ussx)