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?

  • How to prevent RabbitMQ settings to be lost during intermediate steps of a Dockerfile?
  • Docker MongoDB : UserNotFound
  • docker: Is it possible to start native windows sibling containers from within another?
  • SSH tunneling to remote server with docker
  • How to access the metadata of a docker container from a script running inside the container?
  • How to run official mongodb docker storing data to separate host system drive?
  • Basically I’m looking for the best way to make a low level change to every application running in your environment.


  • Docker IPv6: Disable IPv4 in bridge docker0 and docker network
  • Run PHPUnit by terminal with Docker
  • How to provide user defined argument and value in docker run?
  • Read cgroups data without mounting it
  • Docker service Limits and Reservations
  • access host's ssh tunnel from docker container
  • Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.