> So basically you're using docker in place of tar here really. Not even in the slightest. They don't even compare... at all. By using a TAR archive of you de

> So basically you're using docker in place of tar here really. Not even in the slightest. They don't even compare... at all. By using a TAR archive of you deployment files, you're completely side stepping all the benefits of isolating an application into a container, whether it's a monolith or 56 microservices. First up: portability and allowing anyone, on any hardware, and any OS to run the application with a single command. All they need to do is install Docker and "docker run" will do the rest. With a TAR file based deployment, they need TAR, they need to know how-to deploy the application and manage the files; they may need some runtime on their system like Ruby, Python or NodeJS; and they cannot restrict the resources the application is using... On the back of the above: for your developers to fire up a new version of the application that a collogue may have written requires muddling around in Git and using branches -- this interrupts work flows and can lead to lose of work if "git stash" isn't used right. With a container: they just run it. Secondly you can restrict the resources the application is using inside of a container much easier than you can with one that is not. I'll make one final point here: Docker Compose. You're missing out on a lot of free stuff here. It's so easy to write a Docker Compose file that brings up everything needed by the application - databases, caches, mocked APIs - allowing anyone in your organisation to bring up the application on their laptop and play with it, including the CEO, DBAs, QA, the receptionist. You're ignoring all of this because... well I can't put my finger on it, to be honest. Maybe you enjoy hurting your self? lol Good luck. I don't feel it's worth responding to future comments on this thread. You're clearly unwilling to listen or try new things. > It's similar to how I deploy the projects. I use fabric (for copying files and executing remote commands, e.g. for db migration) in place of a makefile, but the idea is the same. Haha! No, they're not the same idea. One is idempotent and the other is not. That's a big differences. And why Fabric? Why not Ansible or Salt Stack? Man what a way to make your life more difficult for no reason.