{"action":"created","issue":{"url":"https://api.github.com/repos/francescou/docker-compose-ui/issues/6","labels_url":"https://api.github.com/repos/francescou/docker-compose-ui/issues/6/labels{/name}","comments_url":"https://api.github.com/repos/francescou/docker-compose-ui/issues/6/comments","events_url":"https://api.github.com/repos/francescou/docker-compose-ui/issues/6/events","html_url":"https://github.com/francescou/docker-compose-ui/issues/6","id":103457343,"number":6,"title":"Issues with current folder references","user":{"login":"tarlabs","id":5294143,"avatar_url":"https://avatars.githubusercontent.com/u/5294143?v=3","gravatar_id":"","url":"https://api.github.com/users/tarlabs","html_url":"https://github.com/tarlabs","followers_url":"https://api.github.com/users/tarlabs/followers","following_url":"https://api.github.com/users/tarlabs/following{/other_user}","gists_url":"https://api.github.com/users/tarlabs/gists{/gist_id}","starred_url":"https://api.github.com/users/tarlabs/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/tarlabs/subscriptions","organizations_url":"https://api.github.com/users/tarlabs/orgs","repos_url":"https://api.github.com/users/tarlabs/repos","events_url":"https://api.github.com/users/tarlabs/events{/privacy}","received_events_url":"https://api.github.com/users/tarlabs/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2015-08-27T08:42:53Z","updated_at":"2015-08-27T14:48:06Z","closed_at":"2015-08-27T14:48:06Z","body":"I have a docker-compose.yml which refers to the folders in current directory\r\n\r\n```yaml\r\nbase:\r\n  image: centos:6.6\r\n  entrypoint: /bin/bash\r\n  volumes:\r\n    - ./scripts:/scripts\r\n  command: /scripts/infinite.sh\r\n```\r\nThe file is there in the ./scripts folder but your API doesn't bring it up fine and I get an error that infinite.sh file is not there. Since you are running it in a docker-container I believe the mapping doesn't happen properly"},"comment":{"url":"https://api.github.com/repos/francescou/docker-compose-ui/issues/comments/135457161","html_url":"https://github.com/francescou/docker-compose-ui/issues/6#issuecomment-135457161","issue_url":"https://api.github.com/repos/francescou/docker-compose-ui/issues/6","id":135457161,"user":{"login":"francescou","id":1886545,"avatar_url":"https://avatars.githubusercontent.com/u/1886545?v=3","gravatar_id":"","url":"https://api.github.com/users/francescou","html_url":"https://github.com/francescou","followers_url":"https://api.github.com/users/francescou/followers","following_url":"https://api.github.com/users/francescou/following{/other_user}","gists_url":"https://api.github.com/users/francescou/gists{/gist_id}","starred_url":"https://api.github.com/users/francescou/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/francescou/subscriptions","organizations_url":"https://api.github.com/users/francescou/orgs","repos_url":"https://api.github.com/users/francescou/repos","events_url":"https://api.github.com/users/francescou/events{/privacy}","received_events_url":"https://api.github.com/users/francescou/received_events","type":"User","site_admin":false},"created_at":"2015-08-27T14:48:06Z","updated_at":"2015-08-27T14:48:06Z","body":"I've made several tests, I came to the conclusion that the problem is caused by Compose itself while running inside a container.\r\n\r\nI've tried to mount a volume with docker-compose inside a container based on the official centos image and then another one based on [dduportal/docker-compose](https://hub.docker.com/r/dduportal/docker-compose/). In both cases I didn't manage to mount a volume.\r\n\r\nI've also found some information about the problem on the following links: [dduportal/docker-compose/#volumes-relative-and-absolute](https://hub.docker.com/r/dduportal/docker-compose/#volumes-relative-and-absolute) (check also the workaround suggested by kayvan in the comments) and https://github.com/dduportal/dockerfiles/issues/5\r\n\r\nI will close the issue, feel free to reopen if necessary."}}