{"action":"closed","issue":{"url":"https://api.github.com/repos/docker/docker/issues/14473","labels_url":"https://api.github.com/repos/docker/docker/issues/14473/labels{/name}","comments_url":"https://api.github.com/repos/docker/docker/issues/14473/comments","events_url":"https://api.github.com/repos/docker/docker/issues/14473/events","html_url":"https://github.com/docker/docker/issues/14473","id":93839010,"number":14473,"title":"Proposal: Lock out access to containers","user":{"login":"aleemb","id":46616,"avatar_url":"https://avatars.githubusercontent.com/u/46616?v=3","gravatar_id":"","url":"https://api.github.com/users/aleemb","html_url":"https://github.com/aleemb","followers_url":"https://api.github.com/users/aleemb/followers","following_url":"https://api.github.com/users/aleemb/following{/other_user}","gists_url":"https://api.github.com/users/aleemb/gists{/gist_id}","starred_url":"https://api.github.com/users/aleemb/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/aleemb/subscriptions","organizations_url":"https://api.github.com/users/aleemb/orgs","repos_url":"https://api.github.com/users/aleemb/repos","events_url":"https://api.github.com/users/aleemb/events{/privacy}","received_events_url":"https://api.github.com/users/aleemb/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-07-08T16:53:33Z","updated_at":"2015-07-10T15:19:14Z","closed_at":"2015-07-10T15:19:14Z","body":"I took on Docker today with the hope that I could use it as a sort of application binary: Allow users to run the container and consume the services provided by it but not allow them access inside the container.\r\n\r\nMy primary use-case is that I would like to be able to deploy small enterprise services as docker containers, as opposed to deploying entire hardware systems behind lock and key.\r\n\r\nMy other use-case is also that I want to do have docker containers run as a sandbox for critical but dependent services without providing access to junior developers or sub-contractors. Typically this can be achieved by running certain services on the local intranet (on staging/development servers) but having these services run locally would be really helpful.\r\n\r\nIs there anything I can do to achieve this today? I don't need a fool-proof system but something that would be reasonably difficult to snoop inside."}}