{"action":"created","issue":{"url":"https://api.github.com/repos/docker/compose/issues/3223","repository_url":"https://api.github.com/repos/docker/compose","labels_url":"https://api.github.com/repos/docker/compose/issues/3223/labels{/name}","comments_url":"https://api.github.com/repos/docker/compose/issues/3223/comments","events_url":"https://api.github.com/repos/docker/compose/issues/3223/events","html_url":"https://github.com/docker/compose/issues/3223","id":143892670,"number":3223,"title":"The docker-compose volumes_from does not persist data across container restarts.","user":{"login":"kvramana","id":5739731,"avatar_url":"https://avatars.githubusercontent.com/u/5739731?v=3","gravatar_id":"","url":"https://api.github.com/users/kvramana","html_url":"https://github.com/kvramana","followers_url":"https://api.github.com/users/kvramana/followers","following_url":"https://api.github.com/users/kvramana/following{/other_user}","gists_url":"https://api.github.com/users/kvramana/gists{/gist_id}","starred_url":"https://api.github.com/users/kvramana/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/kvramana/subscriptions","organizations_url":"https://api.github.com/users/kvramana/orgs","repos_url":"https://api.github.com/users/kvramana/repos","events_url":"https://api.github.com/users/kvramana/events{/privacy}","received_events_url":"https://api.github.com/users/kvramana/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/docker/compose/labels/kind/question","name":"kind/question","color":"cc317c"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2016-03-28T04:57:44Z","updated_at":"2016-04-05T05:11:25Z","closed_at":null,"body":"I am on Mac OS X running docker version 1.10.3, build 20f81dd and docker-compose version 1.6.2, build 4d72027.\r\n\r\nIn my `YML` file, i have two services. The first is a data only container service which is referenced from a second container (mongodb) service using `volumes_from` directive. I do some operations in the second container (mongodb) service. I connect to mongodb container service, and it correctly shows data from my operations.\r\n\r\nNow i do a `docker-compose down`, wait few minutes, and then `docker-compose up` command. I was expecting to not lose data from previous operations but it is lost. If i do a `docker stop` followed by `docker start`, i see data from prior operations and don't lose it though.\r\n\r\nIs this a known bug and is there a work around for this bug please?"},"comment":{"url":"https://api.github.com/repos/docker/compose/issues/comments/205645772","html_url":"https://github.com/docker/compose/issues/3223#issuecomment-205645772","issue_url":"https://api.github.com/repos/docker/compose/issues/3223","id":205645772,"user":{"login":"kvramana","id":5739731,"avatar_url":"https://avatars.githubusercontent.com/u/5739731?v=3","gravatar_id":"","url":"https://api.github.com/users/kvramana","html_url":"https://github.com/kvramana","followers_url":"https://api.github.com/users/kvramana/followers","following_url":"https://api.github.com/users/kvramana/following{/other_user}","gists_url":"https://api.github.com/users/kvramana/gists{/gist_id}","starred_url":"https://api.github.com/users/kvramana/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/kvramana/subscriptions","organizations_url":"https://api.github.com/users/kvramana/orgs","repos_url":"https://api.github.com/users/kvramana/repos","events_url":"https://api.github.com/users/kvramana/events{/privacy}","received_events_url":"https://api.github.com/users/kvramana/received_events","type":"User","site_admin":false},"created_at":"2016-04-05T05:11:24Z","updated_at":"2016-04-05T05:11:24Z","body":"I used named volume, still lost data, i mean the volume must have been stashed away, but didn't get auto-mounted upon next `up` operation. So i think, using `stop` instead of `down` is the only option here."}}