> Having to "docker exec" to get a shell in a running container vs just running the command (in dev) or sshing into the server (in prod). If this bother you, t

> Having to "docker exec" to get a shell in a running container vs just running the command (in dev) or sshing into the server (in prod). If this bother you, take a look at some 3rd party docker management ui such as portainer (vanilla docker) or k9s (kubernetes). These tools will let you navigate and launch shell on your container quickly. Very useful if you have tons of apps running in your node. > Tests taking 3:30 min to run with docker vs 30 secs without. And then of course, you don't just run tests once but many times, leading to tens of minutes on a given day where I'm just twisting my thumbs. In my case, I don't use docker in development phase. I test in local environment and only build the images when it's ready for deployment. > Having to even spend time learning how to debug Python code inside a locally running docker container. I never had to do this anymore. I just hook sentry or newrelic and they'll log exception stack traces that I can use to figure out the issue without live-debugging the app. > Having to deal with disk space issues caused by old docker images on my 500gb hdd. Yes, disk usage is one of the drawback of using docker. It's especially suck pruning images on busy servers with spinning rust. On ssd, pruning is not as slow though.