{"action":"created","issue":{"url":"https://api.github.com/repos/rancher/os/issues/706","labels_url":"https://api.github.com/repos/rancher/os/issues/706/labels{/name}","comments_url":"https://api.github.com/repos/rancher/os/issues/706/comments","events_url":"https://api.github.com/repos/rancher/os/issues/706/events","html_url":"https://github.com/rancher/os/issues/706","id":123583776,"number":706,"title":"Defining a new system-docker volume","user":{"login":"colebrumley","id":5015139,"avatar_url":"https://avatars.githubusercontent.com/u/5015139?v=3","gravatar_id":"","url":"https://api.github.com/users/colebrumley","html_url":"https://github.com/colebrumley","followers_url":"https://api.github.com/users/colebrumley/followers","following_url":"https://api.github.com/users/colebrumley/following{/other_user}","gists_url":"https://api.github.com/users/colebrumley/gists{/gist_id}","starred_url":"https://api.github.com/users/colebrumley/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/colebrumley/subscriptions","organizations_url":"https://api.github.com/users/colebrumley/orgs","repos_url":"https://api.github.com/users/colebrumley/repos","events_url":"https://api.github.com/users/colebrumley/events{/privacy}","received_events_url":"https://api.github.com/users/colebrumley/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":5,"created_at":"2015-12-23T01:07:11Z","updated_at":"2016-01-05T05:38:16Z","closed_at":null,"body":"I am attempting to build on @pwFoo's work from #601, #567, and #542 on a Convoy plugin container. I'd really prefer to use system-docker since I don't want the Convoy client to be intimately linked with the Docker daemon for which it's providing volumes. The other catch is that it'd be great if that service could expose the Convoy binaries as volumes that are included in `command-volumes` or `user-volumes` so that they're exposed to the console by default.\r\n\r\nRight now I have a container that runs fine in terms of providing driver-level access to Convoy from user-docker, but I'm having trouble figuring out how to map the binaries into a console that doesn't require modifying it (so that I could eventually PR the service into os-services).\r\n\r\nPutting the binaries into one of the `user-volumes` is something I've considered, but then you have to modify the console's `$PATH` and move the binaries there after the volume exists instead of exposing them where they lay.\r\n\r\nSince they don't exist on the buildroot base filesystem, I obviously can't map them with `/usr/bin/convoy:/usr/bin/convoy:ro`.  Do I have to build a custom os-base to do this, or is there a way to include volumes in `all-volumes` from a service YAML? If not, would it make sense to add a `io.rancher.os.volumes.expose` tag or something? It would make adding system services for plugins a lot easier and discourage (me from) modifying the base unnecessarily."},"comment":{"url":"https://api.github.com/repos/rancher/os/issues/comments/168904240","html_url":"https://github.com/rancher/os/issues/706#issuecomment-168904240","issue_url":"https://api.github.com/repos/rancher/os/issues/706","id":168904240,"user":{"login":"pwFoo","id":333408,"avatar_url":"https://avatars.githubusercontent.com/u/333408?v=3","gravatar_id":"","url":"https://api.github.com/users/pwFoo","html_url":"https://github.com/pwFoo","followers_url":"https://api.github.com/users/pwFoo/followers","following_url":"https://api.github.com/users/pwFoo/following{/other_user}","gists_url":"https://api.github.com/users/pwFoo/gists{/gist_id}","starred_url":"https://api.github.com/users/pwFoo/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/pwFoo/subscriptions","organizations_url":"https://api.github.com/users/pwFoo/orgs","repos_url":"https://api.github.com/users/pwFoo/repos","events_url":"https://api.github.com/users/pwFoo/events{/privacy}","received_events_url":"https://api.github.com/users/pwFoo/received_events","type":"User","site_admin":false},"created_at":"2016-01-05T05:38:16Z","updated_at":"2016-01-05T05:38:16Z","body":"I use the default convoy and also user-docker volume path. It's persistent and no change is needed.\r\n\r\nTo avoid changes we need Wirkung mapping, but /usr/local/bin (is inside $PATH) doesn't exist at RancherOS and /usr/bin used the file isn't available Form the host. So I haven't found a better way.\r\nThe alias is needed to manage Volumens. Add / create can be done from \"docker run\" \r\n\r\nI would also prefer a mapping to the host, but it seems to be difficult.\r\nI would set some more configs Mike the alias in another system-docker container (firewall rules, maybe static routes,...)\r\n\r\nWould be great to get mapping working for example by using /usr/local/bin for mapping...\r\nHaven't tested this directory because it doesn't exist, but it could be created during boot (container, cloud config) andcshould be tested."}}