I am starting to use CoreOS (on AWS ECS). After starting my first container, I see this in journalctl :
Could not generate persistent MAC address for vethXXXX: No such file or directory
There is more context. I deleted the time and instance information, but all this in one second. Please note that there are two different veth entries. I do not know what it means.
systemd[1]: Started docker container 1234 systemd[1]: Starting docker container 1234 dockerd[595]: time="2015-07-23T23:30:52Z" level=info msg="GET /v1.17/containers/1234/json" dockerd[595]: time="2015-07-23T23:30:52Z" level=info msg="+job container_inspect(1234)" systemd-timesyncd[473]: Network configuration changed, trying to establish connection.systemd-udevd[7501]: Could not generate persistent MAC address for vethYYYY: No such file or directory kernel: device vethXXXX entered promiscuous mode kernel: IPv6: ADDRCONF(NETDEV_UP): vethXXXX: link is not ready systemd-udevd[7508]: Could not generate persistent MAC address for vethXXXX: No such file or directory systemd-networkd[497]: vethXXXX: Configured kernel: eth0: renamed from vethYYYY kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethXXXX: link becomes ready kernel: docker0: port 2(vethXXXX) entered forwarding state kernel: docker0: port 2(vethXXXX) entered forwarding state systemd-networkd[497]: vethXXXX: Gained carrier
I found a discussion about this error in Ubuntu, and it boils down to removing the udev rule , which does not seem to exist on CoreOS. It discusses iptables with OpenVPN , which doesn't seem to apply. Here is the bridge rule for LXC on Ubuntu . Again, I don’t see how to apply it.
I did nothing with the networkd or flannel configuration. If there is a problem in this area, I need specific steps to fix it for use in AWS ECS.
coreos amazon-ecs
tedder42
source share