Fig is mounting wrong volumes

[phuongnd08]

I'm having this fig.yml:

db:
  image: postgres:9.3
  volumes:
    - /var/lib/pgsql/9.3/data:/var/lib/postgresql/data
  ports:
    - "5432"

I can run this docker command just fine

docker run --name db3 -P -v /var/lib/pgsql/9.3/data:/var/lib/postgresql/data postgres:9.3

But when I try fig up, it complains that:

Cannot start container d5b358ebcb035253a76bb2a7510a4b683e4dd05d4f91ac29f288259d265e329d: stat /var/lib/docker/devicemapper/mnt/85e8de017e4f2d02a2fd2b26ed3014a1fbced0b8540d22e6cb3b78198fe4bc42/rootfs/var/lib/postgresql/data: no such file or directory

[phuongnd08]

I'm heading over to crane https://github.com/michaelsauter/crane since crane doesn't have that bug. Curiously, would it be possible to merge the two projects? It looks like a waste trying to make just another crane/fig instead of improve it.

[dnephin]

I believe this is issue #328

It has to do with how fig recreates containers. I believe it's not an issue when fig is used with docker 1.0 or 1.2, but there is some problem with intermediate containers and docker 1.1.x

[quentinsf]

I still have the #328 problem with Docker 1.2.

[tomsowerby]

+1
crane and docker (straight-up) handle this fine. Clearly fig has an issue somewhere.
data only volumes seem very unstable.

[Starefossen]

I'm running into similar issue as OP with Fig v1.0.1 and Docker v1.4.1.

[dnephin]

I believe this was fixed in 1.3