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:

  • Building A Docker RPM on Fedora
  • Windows Docker mongo container doesn't work with volume mount
  • Docker-compose mounts are going to work with TCP host?
  • docker PHP-APACHE "You don't have permission to access / on this server”
  • Loopback handle connection issues (and startup crashes)
  • How to fix DNS lame referral error for popular domain such as registry-1.docker.io
    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 data-only container and dealing with new releases
  • How to manage Docker container with dockerode
  • Configure dockerfile with postgres
  • Windows container can't ping Ubuntu container in Swarm
  • How to debug dockerized self-detaching program?
  • How to pass variable as attribute to xml configuration file in Wildfly with Docker
  • Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.