Since docker 1.3.0 / fig 1.0.0 volumes are not mounted when fig up'ing existing containers

[morvans]

Since docker 1.3.0 / fig 1.0.0 (I upgraded both at the same time), I cannot fig up my projects without fig rm'ing before.

If I do fig up on already existing (stopper) containers, volumes specified in fig.yml aren't remounted (default docker mounts instead, so empty dirs).

fig rm && fig up recreates everything correctly but for locally built containers this is pretty time consuming.

[mindo]

This also happens with docker 1.3.1 and fig 1.0.1.
Even more weird is that if a container is ran using fig:

fig run mycontainer bash

The volumes are mounted just fine.

[dnephin]

Are you using volumes or volumes_from? A sample fig.yml may help in debugging.

[mindo]

My fig.yml:

haproxy:
    build: haproxy
    ports:
        - "80:80"
        - "443:443"
    links:
        - ngx

ngx:
    build: ngx-php
    volumes:
        - var/logs/:/var/log
        - ngx-php/etc/:/etc/nginx
        - myapp/:/var/www
    links:
        - percona
        - memcached

memcached:
    build: memcached

percona:
    build: percona
    ports: 
        - "3306:3306"
    volumes:
        - var/mysql/:/var/lib/mysql

All folders defined as volumes are on the same level as fig.yml.

[dnephin]

This seems correct to me. Some things you could try to debug it:

• docker inspect the containers when they're up to see what it's doing
• docker will silently ignore a volume if the path doesn't exist, it's possible it's not doing these relative paths correctly. Maybe try adding a ./ prefix
• paths in the fig.yml are relative to the current working directory, so if you do something like fig -f somepath/fig.yml it might not work (because the paths will be wrong

[nireak]

Perhaps it's a silly question.... but are you using a Virtual Machine to run docker and fig ? If so, do the paths referenced in your "volumes" directives exists inside the VM?

[mindo]

cd /to/folder/with/fig.yml

• fig up

    "Volumes": {
        "/etc/nginx": "/var/lib/docker/vfs/dir/6b04e7ee535de76bfd359ad1c08fbe35db3e435c2301c464a7390ba67cfefe63",
        "/var/log": "/var/lib/docker/vfs/dir/17b86c34458c046e15709731c3e3c760e2c766ce113c5b2fd0f7de9aafdcc17b",
        "/var/www": "/var/lib/docker/vfs/dir/11a480315b57b48c6b7f5abaada5741a5656e5febdd3365e40e62f04e94f3be2"
    },

• fig run ngx bash

    "Volumes": {
        "/etc/nginx": "/mnt/HG/docker/ngx-php/etc",
        "/var/log": "/mnt/HG/docker/var/logs",
        "/var/www": "/mnt/HG/docker/myapp"
    },

I am running this directly on my notebook (ubuntu 14.10, no virtual machine).
I also tried:

ngx:
    build: ngx-php
    volumes:
        - ./var/logs/:/var/log
        - ./ngx-php/etc/:/etc/nginx
        - ./myapp/:/var/www

and

ngx:
    build: ngx-php
    volumes:
        - /mnt/HG/docker/var/logs/:/var/log
        - /mnt/HG/docker/ngx-php/etc/:/etc/nginx
        - /mnt/HG/docker/myapp/:/var/www

and neither worked.

[dnephin]

@mindo this looks like a similar issue to #613. fig up will copy volumes from the previous container when it recreates them. I think if you do: fig stop && fig rm --force -v ngx it should remove those volumes and the next time you create it, it should mount the correct host volumes.

[mindo]

@dnephin yes, doing

fig stop && fig rm && fig build

solves it but only until the next reboot/service docker restart.

Test run:

fig rm
fig build
fig up

Volumes are mounted just fine.

fig stop
fig up

Volumes still work.

fig stop
service docker stop
service docker start
fig up

Volumes fail to mount! But running:

fig run ngx

The Volumes work without problems.

[schickling]

Same here. Any progress on this?

[morvans]

FWIW, the issue seems fixed for me with docker 1.3.2 / fig 1.0.1

[schickling]

I'm using docker 1.3.2 / fig 1.0.1. Still doesn't work for me.

[morvans]

@schickling : yeah, spoke too soon, it still doesn't work for me either eventually.