fig up complains about nonexistent open file descriptors

[amackera]

When trying to fig up, it fails complaining with the following:

Cannot start container 298c03e05b4eec8a3268b0aa36467f4649d831e68aae08fb3c6e4382e9b8b2bd: finalize namespace close open file descriptors open /proc/self/fd: no such file or directory

My fig.yml looks like this:

db: 
 build: ./mysql 
 volumes: /home/amackera/data/mysql:/var/lib/mysql 
 ports: 
 - "3306:3306" 

thm: 
 build: ./app 
 volumes: /home/amackera/work/vm/vagrant/projects/thm/THM:/var/www/app 
 ports: 
 - "8100:8100" 
 links: 
 - db 
 - broker 
 - cache 

broker: 
 build: ./rabbitmq 
 ports: 
 - "5673:5672" 
 - "15673:15672" 

cache: 
 build: ./memcached 
 ports: 
 - "11211:11211" 

cottontail: 
 build: ./cottontail 
 volumes: /home/amackera/work/vm/vagrant/projects/thm/Cottontail:/var/www/cottontail
 ports: 
 - "8001:8001" 
 links: 
 - broker 

worker: 
 build: ./worker 
 volumes: /home/amackera/work/vm/vagrant/projects/thm/THM:/var/www/app 
 links: 
 - db 
 - broker 
 - cache 

Also, after running fig up there are a bunch of empty directories named a and b, etc. in the directory that I keep my fig.yml file.

Any ideas?

Tested with fig version 0.5.0 and 0.5.1, and with docker version 1.1.0 and 1.1.1.

[aanand]

The problem is your volumes keys. They need to be arrays:

db: 
 build: ./mysql 
 volumes:
 - /home/amackera/data/mysql:/var/lib/mysql 
 ports: 
 - "3306:3306"

See #129 - we need to be validating this stuff.

[intellix]

Also getting that same error message on OSX using Fig 0.5.2 but my volumes is an array. In fact, I still get the error message even if I comment most stuff out and just have the build line

deploy:
 build: deploy/build

postgres:
 build: ./postgres/build
 ports:
 - "5432:5432"
 volumes:
 - /Users/dominicwatson/Dropbox/Docker/app/xyz/postgres/data:/var/lib/postgresql

redis:
 image: redis

nginx:
 build: ./nginx/build
 links:
 - postgres
 - redis
 ports:
 - "80:80"
 - "443:443"
 volumes:
 - /Users/dominicwatson/Dropbox/Docker/app/xyz/nginx:/data

[djmaze]

I had to fig rm one time to recover from this problem. So that fig does not try to reuse the (badly defined) volumes from the previous containers. Does that help, @intellix?

[intellix]

Well, I tried it on my work computer and it worked straight away. Just got home and fig rm seems to have done the trick as well. I suppose there should be issue for cleaning up broken runs.
Thanks so much, you've saved me hours of debugging and begging on deaf ears for help via IRC

[Stono]

This just caught me out too. +1 for cleaning up changes in volumes

[dnephin]

I believe #711 would fix it

[ChrisChinchilla]

Updating things, docker-compose rm also fixed my similar problem.