Docker in itself, apart from everything else, is not that hard to setup. But you have to look at the bigger picture here. Maybe the deployment is on "pet serve

Docker in itself, apart from everything else, is not that hard to setup. But you have to look at the bigger picture here. Maybe the deployment is on "pet servers" and not on-demand, which means if you are a responsible admin and have a nftables config you need to analyze how docker will mess up your rules (or why it is not working). Maybe you don’t want to lose time setting up an artifactory, and a docker registry with proper access controls. Maybe you don’t want to have to focus on the ops side of things until you actually need it. Yes that may mean losing time later when you need it fast, but at the same time this can be done iteratively when things are ramping up. From experience at a previous workplace, using docker as part of your local development process can be a huge PITA, and getting developers to adopt it without grumbling and complaining about it every day is also a hurdle. Given enough computers, you will get weird network errors, some borked modules due to an upgrade, some containers refusing to die, etc… I am not saying it cannot be done, and in the general case docker mostly works without (too many) glitches, but it is always another layer that hinders your productive work. (also, "docker" in production nowadays is mostly a shortcut for k8s, and that is a whole new amount of investment required)