search

ibuildthecloud / systemd-docker

Wrapper for "docker run" to handle systemd quirks
Apache License 2.0
721 stars 111 forks source link

journal plagued with log lines #31

Open sebelk opened 9 years ago

sebelk commented 9 years ago

I've found that systemd is full of lines like that when I issue journalctl -f

jul 09 21:13:47 newhope.belkin.home docker[1430]: time="2015-07-09T21:13:47-03:00" level=info msg="GET /v1.11/containers/35f101d97881e543d40370ee4242216dfb88103f2947c0446ad0ad03a1bcd810/json" jul 09 21:13:47 newhope.belkin.home docker[1430]: time="2015-07-09T21:13:47-03:00" level=info msg="+job container_inspect(35f101d97881e543d40370ee4242216dfb88103f2947c0446ad0ad03a1bcd810)" jul 09 21:13:47 newhope.belkin.home docker[1430]: time="2015-07-09T21:13:47-03:00" level=info msg="-job container_inspect(35f101d97881e543d40370ee4242216dfb88103f2947c0446ad0ad03a1bcd810) = OK (0)" jul 09 21:13:48 newhope.belkin.home docker[1430]: time="2015-07-09T21:13:48-03:00" level=info msg="GET /v1.11/containers/35f101d97881e543d40370ee4242216dfb88103f2947c0446ad0ad03a1bcd810/json" jul 09 21:13:48 newhope.belkin.home docker[1430]: time="2015-07-09T21:13:48-03:00" level=info msg="+job container_inspect(35f101d97881e543d40370ee4242216dfb88103f2947c0446ad0ad03a1bcd810)" jul 09 21:13:48 newhope.belkin.home docker[1430]: time="2015-07-09T21:13:48-03:00" level=info msg="-job container_inspect(35f101d97881e543d40370ee4242216dfb88103f2947c0446ad0ad03a1bcd810) = OK (0)" jul 09 21:13:49 newhope.belkin.home docker[1430]: time="2015-07-09T21:13:49-03:00" level=info msg="GET /v1.11/containers/35f101d97881e543d40370ee4242216dfb88103f2947c0446ad0ad03a1bcd810/json" jul 09 21:13:49 newhope.belkin.home docker[1430]: time="2015-07-09T21:13:49-03:00" level=info msg="+job container_inspect(35f101d97881e543d40370ee4242216dfb88103f2947c0446ad0ad03a1bcd810)" jul 09 21:13:49 newhope.belkin.home docker[1430]: time="2015-07-09T21:13:49-03:00" level=info msg="-job container_inspect(35f101d97881e543d40370ee4242216dfb88103f2947c0446ad0ad03a1bcd810) = OK (0)

I have a configuration as follows:

# cat /etc/systemd/system/kanboard.service 
[Unit]
Description=kanboard
After=docker.service
Requires=docker.service
`
[Service]
ExecStart=/opt/bin/systemd-docker --cgroups name=systemd --cgroups=cpu run --rm -p 192.168.0.250:443:443    --volumes-from  data  --name %n sebelk/https 
Restart=always
RestartSec=10s
Type=notify
NotifyAccess=all
TimeoutStartSec=120
TimeoutStopSec=15

[Install]
WantedBy=multi-user.target

I've noted no error in running docker, any idea?

Thanks in advance

stuart-warren commented 9 years ago

That is the docker daemon logging to stdout and being captured by the systemd journal, not from your container or systemd-docker.

try adding the option --log-level=warn to the docker daemon (not your kanboard.service), but you might miss useful info

tazjin commented 9 years ago

I definitely recommend bumping the log level, if you have a few containers running this will otherwise cause your journal to rotate constantly. I believe that --log-level was introduced relatively recently (Docker 1.4 or 1.5) so you might have to upgrade.