{"action":"created","issue":{"url":"https://api.github.com/repos/docker/docker/issues/8244","labels_url":"https://api.github.com/repos/docker/docker/issues/8244/labels{/name}","comments_url":"https://api.github.com/repos/docker/docker/issues/8244/comments","events_url":"https://api.github.com/repos/docker/docker/issues/8244/events","html_url":"https://github.com/docker/docker/issues/8244","id":43974397,"number":8244,"title":"unable to write to /proc/self/loginuid with docker 1.2.0, container ubuntu trusty","user":{"login":"apergos","id":4434934,"avatar_url":"https://avatars.githubusercontent.com/u/4434934?v=3","gravatar_id":"","url":"https://api.github.com/users/apergos","html_url":"https://github.com/apergos","followers_url":"https://api.github.com/users/apergos/followers","following_url":"https://api.github.com/users/apergos/following{/other_user}","gists_url":"https://api.github.com/users/apergos/gists{/gist_id}","starred_url":"https://api.github.com/users/apergos/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/apergos/subscriptions","organizations_url":"https://api.github.com/users/apergos/orgs","repos_url":"https://api.github.com/users/apergos/repos","events_url":"https://api.github.com/users/apergos/events{/privacy}","received_events_url":"https://api.github.com/users/apergos/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2014-09-25T22:14:32Z","updated_at":"2015-03-04T17:43:00Z","closed_at":"2015-01-19T23:25:31Z","body":"This is another version of the sshd failure bug.\r\nHost OS: fedora 20\r\nContainer OS: ubuntu 14.04\r\nKernel: 3.15.8-200.fc20.x86_64\r\nlibpam in container: 1.1.8-1ubuntu2\r\n\r\n/proc is mounted rw, checking from within the container, but when I try to sshd in, I get the following complaint:\r\nSep 25 18:22:07 b1c7606d8b13 sshd: pam_loginuid(sshd:session): Error writing /proc/self/loginuid: Operation not permitted\r\n\r\nChecking the ubuntu patches for pam_loginuid.c, I see that it tries to check whether the process is running in the host namespace or not, by comparing the contents of /proc/self/uid_map to \"         0          0 4294967295\\n\" and if they do not match then the process is assumed to be running in a user namespace, where writes may fail, and thus the write error would be ignored.\r\n\r\nThis must not happen for some reason, and indeed when I cat /proc/self/uid_map manually from within the container, it shows  0 0 4294967295  rather than some variant like 0 1000 1000\r\n\r\nWhat am I missing here? Note that I build docker from the stock trusty image, i.e. \"FROM ubuntu:14.04\", and it is not running with any special options or configuration.\r\n\r\nI could comment out the reference to the pam module in the pam sshd settings but I'd rather get to the underlying cause.  Thanks.\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/docker/docker/issues/comments/77206906","html_url":"https://github.com/docker/docker/issues/8244#issuecomment-77206906","issue_url":"https://api.github.com/repos/docker/docker/issues/8244","id":77206906,"user":{"login":"udomsak","id":319024,"avatar_url":"https://avatars.githubusercontent.com/u/319024?v=3","gravatar_id":"","url":"https://api.github.com/users/udomsak","html_url":"https://github.com/udomsak","followers_url":"https://api.github.com/users/udomsak/followers","following_url":"https://api.github.com/users/udomsak/following{/other_user}","gists_url":"https://api.github.com/users/udomsak/gists{/gist_id}","starred_url":"https://api.github.com/users/udomsak/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/udomsak/subscriptions","organizations_url":"https://api.github.com/users/udomsak/orgs","repos_url":"https://api.github.com/users/udomsak/repos","events_url":"https://api.github.com/users/udomsak/events{/privacy}","received_events_url":"https://api.github.com/users/udomsak/received_events","type":"User","site_admin":false},"created_at":"2015-03-04T17:43:00Z","updated_at":"2015-03-04T17:43:00Z","body":"@jfrazelle  The problem still even Docker version 1.5 and way to fix is remove pam_loginuid  \r\notherwise  you cant' login via SSH key  \r\n"}}