volumes_from (docker-compose) seems not to work within vagrant

[Morgy]

Hello,

since it seems that the GitHub repo is not maintained, I'm trying to get help here:

I'm refering to https://github.com/andreaskoch/dockerized-magento which basically works pretty well, but I stumbled upon some issue, I assume.
It seems that "volumes_from" doesn't work.

First some of my docker-compose.yml:

nginx:
  build: docker-images/nginx
  ports:
    - "80:80"
    - "443:443"
  links:
    - "php"
  domainname: ek.local
  environment:
    DOMAIN: ek.local
    VIRTUAL_HOST: ek.local
    MAGENTO_ROOT: /var/www/html/web
    MAGENTO_DEVELOPERMODE: 1
    SSL_CERTIFICATE_PATH: /etc/ssl/certs/ssl-cert-snakeoil.pem
    SSL_CERTIFICATE_KEY_PATH: /etc/ssl/private/ssl-cert-snakeoil.key
  volumes:
    - //vagrant/docker-images/nginx/server.pem:/etc/ssl/certs/ssl-cert-snakeoil.pem
    - //vagrant/docker-images/nginx/server.key:/etc/ssl/private/ssl-cert-snakeoil.key
  volumes_from:
    - php
php:
  build: docker-images/php/5.5-dev
  links:
    - "cache:rediscache"
    - "sessions:redissession"
    - "fullpagecache:redisfullpagecache"
    - "solr:solr"
    - "mysql:mysql"
  volumes:
    - //vagrant:/var/www/html

Well, to cut it short, the "volumes" defined within php (- //vagrant:/var/www/html) works pretty well.
While looking inside the php container I can see my local files at /var/www/html/web but if I take a look into the nginx container which got volumes_from: - php I don't see anything within /var/www/html/web
The two volumes defined for nginx are working too by the way .. just volumes_from doesn't work.

Any help?

[Alvaro Miranda Aguilera]

Hi there

using my memory, I think that happen if nginx start before php.

Option 1.

stop all and start php first then nginx

Option 2, as the volumes in php came from host -> vm -> docker, you
may just copy the same, so nginx and php have same volumes:


What do you think?
Alvaro

> --
> This mailing list is governed under the HashiCorp Community Guidelines -
> https://www.hashicorp.com/community-guidelines.html. Behavior in violation
> of those guidelines may result in your removal from this mailing list.
>
> GitHub Issues: https://github.com/mitchellh/vagrant/issues
> IRC: #vagrant on Freenode
> ---
> You received this message because you are subscribed to the Google Groups
> "Vagrant" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to vagrant-up+...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/vagrant-up/01cc98de-2d2c-4a2e-8d11-8c71945dd431%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

[Morgy]

Hello,

option 1:

Actually the nginx container does start after the php container.
It wouldn't work the other way round, because there would be some error like:
Error response from daemon: Cannot start container vagrant_nginx_1: Cannot link to a non running container: /vagrant_php_1 AS /vagrant_nginx_1/php_1
Error: failed to start containers: [vagrant_nginx_1]



Option 2:

Yeah makes sense and it seems to work (as a "workaround"), but it is not intended to be like this. =/