Handle startup of docker container inside another

I have an application, running in docker container A. Application can use modules, which I want to place in data-only container B. Containers is starting from docker-compose file, where is assigned to get volumes from container B to container A. Than I should restart containers by composer To reach B files on A.

Questions is:

  • Docker, communicating between hosts on different bridges
  • why did the pulling process in docker act like this?
  • cf ic logs Container gives json: cannot unmarshal string into Go value of type []string
  • Docker dotnet image container do not allow me to rebuild after change
  • How to change Docker default subnet size?
  • Docker Build can't find pip
    1. Can I just start container B and don’t restart container A, if path to volume form B is not exist?
    2. How can I handle inside of container A start/stop of container B, to process install of modules?

  • Docker-compose check if mysql connection is ready
  • AWS Mesosphere: parameters for docker daemon
  • Cloudera support for docker container or Docker support for CM 5 image
  • Flask app doesn't retrieve data from same database as unit tests
  • docker secrets for configuration files
  • How to _directly_ COPY files to “Program Files (x86)” folder in a Windows container?
  • Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.