[scarlac]

Docker is very well suited for local development and testing, particularly since the launch of Docker for Mac and Windows. It makes utilities like MAMP less necessary.

But apart from local development, I'd say that depends on your needs. If you want more ease-of-use, and you run a single-server hosting environment with multiple projects, it may be easier to keep doing that without adding Docker. But if you want increased security and better isolation between your projects, Docker is likely a better solution.

In any case, I would strongly recommend that you familiarize yourself with Docker, at least locally. After a while, you can decide if you want to take the leap and use it on your server as well.

[nefasti]

Docker for local development for us been a pain in the butt. - We've hit performance problems with the filesystem, - Problem with caching things like yarn and npm install - The need to constantly rebuild the images for changes to be picked up. - Dificulty dealing with single docker file for prod and testing, making us want to montain 2 docker files.

Probably some bad setup of our part, but we've been using on production with kubernetes and none of those problems.

We're still using the compose to bootstrap database, caching, etc.

[tonyhb]

I don't understand how kubernetes solved your base image issue. That's a clustering system, so by default it can't help.

It sounds as though your setup doesn't work with the immutable filesystems introduced by docker. That's not an issue with docker at all - just something to learn.

I can't imagine dev or deployment without docker any more - all of my tests, yarn installs, dev workflow and prod runs through it.