{"action":"created","issue":{"url":"https://api.github.com/repos/coreos/coreos-github/issues/3","labels_url":"https://api.github.com/repos/coreos/coreos-github/issues/3/labels{/name}","comments_url":"https://api.github.com/repos/coreos/coreos-github/issues/3/comments","events_url":"https://api.github.com/repos/coreos/coreos-github/issues/3/events","html_url":"https://github.com/coreos/coreos-github/issues/3","id":105692621,"number":3,"title":"LOWERLAYERDOWN for docker0 bridge since upgrading to CoreOS766.3.0","user":{"login":"hookenz","id":6227712,"avatar_url":"https://avatars.githubusercontent.com/u/6227712?v=3","gravatar_id":"","url":"https://api.github.com/users/hookenz","html_url":"https://github.com/hookenz","followers_url":"https://api.github.com/users/hookenz/followers","following_url":"https://api.github.com/users/hookenz/following{/other_user}","gists_url":"https://api.github.com/users/hookenz/gists{/gist_id}","starred_url":"https://api.github.com/users/hookenz/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/hookenz/subscriptions","organizations_url":"https://api.github.com/users/hookenz/orgs","repos_url":"https://api.github.com/users/hookenz/repos","events_url":"https://api.github.com/users/hookenz/events{/privacy}","received_events_url":"https://api.github.com/users/hookenz/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2015-09-09T21:57:38Z","updated_at":"2015-09-09T23:19:34Z","closed_at":null,"body":"I've got some odd issues with container networking.  Some services were not responding all of a sudden and I've isolated it to this one machine that is showing the LOWERLAYERDOWN error.\r\n\r\ndocker0@NONE: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state LOWERLAYERDOWN group default\r\n\r\nYet all networks are all up.\r\n\r\nSome googling suggests that recent versions of systemd-network ignore the global ipforward flag and that you have to set it per interface.\r\n\r\nhttps://github.com/docker/docker/issues/14185\r\n\r\nHowever, mine are all in the forward state and UP.  I set the IPForward=kernel against the primary network interface and rebooted and it is still saying \"LOWERLAYERDOWN\".\r\n\r\nSome further investigation and several reboots and despite it saying LOWERLAYERDOWN the containers are able to ping other networks..  confused!  is this LOWERLAYERDOWN message incorrect and should it be ignored?\r\n"},"comment":{"url":"https://api.github.com/repos/coreos/coreos-github/issues/comments/139070218","html_url":"https://github.com/coreos/coreos-github/issues/3#issuecomment-139070218","issue_url":"https://api.github.com/repos/coreos/coreos-github/issues/3","id":139070218,"user":{"login":"hookenz","id":6227712,"avatar_url":"https://avatars.githubusercontent.com/u/6227712?v=3","gravatar_id":"","url":"https://api.github.com/users/hookenz","html_url":"https://github.com/hookenz","followers_url":"https://api.github.com/users/hookenz/followers","following_url":"https://api.github.com/users/hookenz/following{/other_user}","gists_url":"https://api.github.com/users/hookenz/gists{/gist_id}","starred_url":"https://api.github.com/users/hookenz/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/hookenz/subscriptions","organizations_url":"https://api.github.com/users/hookenz/orgs","repos_url":"https://api.github.com/users/hookenz/repos","events_url":"https://api.github.com/users/hookenz/events{/privacy}","received_events_url":"https://api.github.com/users/hookenz/received_events","type":"User","site_admin":false},"created_at":"2015-09-09T23:19:34Z","updated_at":"2015-09-09T23:19:34Z","body":"False alarm.  I've just discovered that this behaviour is normal if there are no containers attached to the bridge.  I just fired up another container that doesn't use --net=host and then the bridge state changed on the host.  So nevermind.  It's all good."}}