With Buddy (http://buddy.works) you can automate everything, even Docker image building... or build application inside Docker container. They have also free Docker-based standalone version - luxury babe :P

Hey Tomasz,

thanks for the comment, but I'm not sure how Buddy solves the local development problem that was outlined in the article...

So this is very interesting, as I have been trying to replicate our nice node.js and python docker developer experiences, and this is the closest I've found, but we do it in a single Dockerfile. In our node and python, the developer will locally use compose to inject a host volume that overrides the source files, and override the CMD java $JAVA_OPTS -Djava.security.egd=file:/dev/./urandom -jar /app.jar to use ./gradlew -t bootRun ( -t or --continuous causes it to reload based on watched files).

Hey Edgewise,

thanks for the comment!

How exactly do you achieve the overriding of the CMD?

Thanks,
Adam

Anything after the image in the docker run command overrides CMD

Your Docker image must have either an ENTRYPOINT or CMD defined to run. If you have only one, then they behave the same. If you have both, then ENTRYPOINT is executed with CMD as arguments. There's the exec form and the shell form of CMD, ENTRYPOINT, and the exec form is the preferred.
This is a pretty good article summarizing all the differences:
http://www.johnzaccone.io/e...

Cool, thanks for the info!

We have setup a CI CD pipeline with docker cloud using different databases, Java and python servers. This is exactly the problem we are also facing now. I would have expected the benefits of developing locally fast in the exact same enviroment but it's not working out. We are now developing locally without docker and on every push to our Github a new docker image is build and deployed.

Thanks for the comment. It's good to know that I'm not the only one running into this problem.

Did you guys try the multiple containers approach?