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?

  • Docker Remote API exec: Command exit code
  • Docker-machine create: Error with pre-create check: “Hyper-v commands have to be run as an Administrator”
  • Error “No module named MySQLdb” on docker
  • wget truncating url inside docker image
  • Docker volume option create folder as “root” user
  • Passing docker container IP address to container
  • Basically I’m looking for the best way to make a low level change to every application running in your environment.


  • Docker compose v2 containers not finding each other (though v1 does)
  • Fluent docker tail vs docker fluentd logging driver
  • NuGet with Mono on Linux: Error getting response stream
  • Docker: Error starting container: Unable to load the AUFS module
  • docker-ce 17.06.0-ce failed to pull from private registry mirror
  • How to use Docker to obtain JDK + MySQL + Tomcat container?
  • Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.