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:

  • Unable to build docker image, “must be a root user”
  • what's the best way to let kubenetes pods communicate with each other?
  • Using Nginx as micro service API gateway
  • datadog agent not reachable from inside docker container
  • Downloading file from S3 using boto3 inside Docker fails
  • Caching Maven parent in offline build
    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?

  • How to back up docker swarm mode service configuration for disaster recovery
  • Is there a way to store files on the docker host which will survive host restarts?
  • Proper way of reporting performance data for C# application in a Container (Docker)
  • Docker+Laravel installation
  • dockerfile is not creating directory and copying files?
  • Xdebug ignores breakpoints in Netbeans for Php project created inside Docker container
  • Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.