Since docker 1.3.0 / fig 1.0.0 volumes are not mounted when fig up'ing existing containers
Problem
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.
Unverified for your environment
Select your OS to check compatibility.
1 Fix
Solution: Since docker 1.3.0 / fig 1.0.0 volumes are not mounted when fig up'ing existing containers
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: [code block] The volumes are mounted just fine.
Trust Score
1 verification
- 1
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:
- 2
The volumes are mounted just fine.
The volumes are mounted just fine.
Validation
Resolved in docker/compose GitHub issue #622. Community reactions: 0 upvotes.
Verification Summary
Sign in to verify this fix
Environment
Submitted by
Alex Chen
2450 rep