Can you efficiently change a lower level Docker container, without rebuilding all the apps that rely on it?

I’ve seen that you can layer Docker containers. As an example, lets say we had a set up with a Java container at the base, say running Java 6, a Tomcat container running on top of the Java container, and say 400 unique application containers running on top of the Tomcat container.

Is there a way to switch to Java 7, replace the Java 6 container with a Java 7 container, and not have to rebuild 400 applications? and then deploy 400 applications? and then shut down the original 400 applications?

  • Invalid type in docker-compose volume
  • Mysql socket is missing in my homestead docker container
  • Nexus 3: “Remote Connection Pending…” for docker hub
  • Minimal configuration for Apache reverse proxy in Docker container
  • C source files not allowed when not using cgo or SWIG: sqlite3-binding.c
  • bcrypt fails to install inside docker
  • Basically I’m looking for the best way to make a low level change to every application running in your environment.


  • Docker build & deploy on Jenkins takes increasingly long amount of time
  • Git clone repo in Dockerfile
  • docker-credential-osxkeychain wants to use your confidential information
  • minimum caps to run pbuilder in docker >= 1.2.0
  • Make Docker for mac listen on a tcp port
  • MySQL EF6 with MVC5 and DNX
  • Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.