How do you share volumes between Docker containers in an Elastic Beanstalk application?

I’m trying to share data between two Docker containers that are running in a multicontainer AWS EC2 instance.

Normally, I would specify the volume as a command flag when I ran the container, ie: docker run -p 80:80 -p 443:443 --link Widget:Widget --volumes-from Widget --name Nginx1 -d nginx1 to share a volume from Widget to Nginx1.

  • Connection refused with kubectl on EC2 ubuntu instance?
  • kubernetes and debugging it in general
  • Elastic Beanstalk, Docker and Continuous integration
  • AWS elastic beanstalk not mounting docker volumes
  • Why I receive permission denied in Docker deployment?
  • Best way to to implement Spark + AWS + Caffe/CUDA?
  • However, since Elastic Beanstalk requires you to specify your Docker configuration in a file, and then handles running your docker containers internally, I haven’t been able to figure out how to share data volumes between containers.

    Note that I’m not trying to share data from the EC2 instance into a Docker container — this part seems to work fine; rather, I would like to share data directly from one Docker container to another. I know that docker container volumes are shared with the host at "/var/lib/docker/volumes/fac362...80535" etc., but since this location is not static I don’t know how I would reference it in the file.

    Has anyone found a solution or a workaround?

    More info on and the config EB is looking for here:


  • Docker Container: Did anyone use G11DockerWp to clone WordPress site?
  • Bluemix Dev Ops: Building a project with private git submodules
  • Do I really need docker swarm?
  • Dynamic Scalable and adaptive architecture
  • Reverse proxy nginx and Express server returning 502
  • How to allow websockets to specific subdomain behind an nginx proxy?
  • 2 Solutions collect form web for “How do you share volumes between Docker containers in an Elastic Beanstalk application?”

    To accomplish what you want, you need to use the volumesFrom parameter correctly. You need to make sure to expose the volume with a VOLUME command for the container sharing its internal data.

    Here’s an example Dockerfile which I used to bundle some static files for serving via a webserver:

    FROM tianon/true
    COPY build/ /opt/static
    VOLUME ["/opt/static"]

    Now the relevant parts of the

        "name": "staticfiles",
        "image": "mystaticcontainer",
        "essential": false,
        "memory": "16"
        "name": "webserver,
        "volumesFrom" : [
                "sourceContainer": "staticfiles"

    Note that you don’t need any volumes entry in the root of the file, since the volume is only shared between the two containers, and not persisted on the host. You also don’t need any specific mountPoints key in the container definition holding the volume to be shared, as the container with volumesFrom automatically picks up all the volumes from the referred container. In this example, all the files in /opt/static in the staticfiles container will also be available to the webserver container at the same location.

    From the AWS docs I found this:

    You can define one or more volumes on a container, and then use the
    volumesFrom parameter in a different container definition (within the
    same task) to mount all of the volumes from the sourceContainer at
    their originally defined mount points.

    The volumesFrom parameter applies to volumes defined in the task
    definition, and those that are built into the image with a Dockerfile.

    Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.