{"action":"opened","issue":{"url":"https://api.github.com/repos/projectatomic/atomic-site/issues/111","labels_url":"https://api.github.com/repos/projectatomic/atomic-site/issues/111/labels{/name}","comments_url":"https://api.github.com/repos/projectatomic/atomic-site/issues/111/comments","events_url":"https://api.github.com/repos/projectatomic/atomic-site/issues/111/events","html_url":"https://github.com/projectatomic/atomic-site/issues/111","id":70681232,"number":111,"title":"New Blog Summission","user":{"login":"rhatdan","id":2000835,"avatar_url":"https://avatars.githubusercontent.com/u/2000835?v=3","gravatar_id":"","url":"https://api.github.com/users/rhatdan","html_url":"https://github.com/rhatdan","followers_url":"https://api.github.com/users/rhatdan/followers","following_url":"https://api.github.com/users/rhatdan/following{/other_user}","gists_url":"https://api.github.com/users/rhatdan/gists{/gist_id}","starred_url":"https://api.github.com/users/rhatdan/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rhatdan/subscriptions","organizations_url":"https://api.github.com/users/rhatdan/orgs","repos_url":"https://api.github.com/users/rhatdan/repos","events_url":"https://api.github.com/users/rhatdan/events{/privacy}","received_events_url":"https://api.github.com/users/rhatdan/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-04-24T12:45:15Z","updated_at":"2015-04-24T12:45:15Z","closed_at":null,"body":"#Docker logging to container output to journald\r\n\r\nDocker has added a new feature to allow alternate logging drivers.\r\n\r\nCurrently in docker-1.6 they support json-file, which is the old default, syslog  or even none.  \r\n\r\nIf you ran your docker daemon with the `--log-driver=syslog` option, any output from a container would go directly to system syslog daemon, and usually end up in /var/log/messages.\r\n\r\nI added a patch to support journald as a logging driver, and it was recently merged.  \r\n\r\nIn docker-1.7 you will have the option to use `--log-driver=journald` on either your docker daemon to cause all of your container logging to go directly to the journal, or you could use the --log-driver=journald on a docker run/create line, so you could get individual containers running with different logging drivers.\r\n\r\nTo test this I setup my docker daemon to run with the following options.  \r\n\r\n```docker -d --selinux-enabled --log-driver=journald```\r\n\r\nNow I run a simple container.\r\n\r\n```docker run fedora echo \"Dan Walsh was here\"```\r\n\r\nThen I look up the container ID for the newly created container, and I can use journalctl to examine the content.\r\n\r\n```\r\njournalctl MESSAGE_ID=cdf02c627e27\r\n-- Logs begin at Mon 2015-04-06 16:06:42 EDT, end at Fri 2015-04-24 08:40:38 EDT. --\r\nApr 20 15:06:39 dhcp-10-19-62-196.boston.devel.redhat.com docker[27792]: Dan Walsh was here\r\n```\r\n\r\nCurrently docker logs command only works with json-file backend.  But I hope to eventually get the docker daemon to communicate with the journald to get this information.  Of course if anyone wants to take a stab at this, I would welcome your effort.\r\n\r\n\r\n"}}