vyos-cloud-init.git/upstart/cloud-init-container.conf, branch circinus-public-unmaintained (mirror of https://github.com/vyos/vyos-cloud-init.git) https://git.amelek.net/vyos/vyos-cloud-init.git/atom?h=circinus-public-unmaintained 2013-01-31T19:49:22+00:00 upstart/cloud-init-container.conf: ensure /run/network exists 2013-01-31T19:49:22+00:00 Scott Moser smoser@ubuntu.com 2013-01-31T19:49:22+00:00 urn:sha1:1bb72070b70edaa960b3158feba936fbc3687b1f ifquery will exit failure if there is no /run/network directory. normally that would get created by one of network-interface.conf or networking.conf. But, it is possible that we're running before either of those have. remove trailing whitespace 2012-09-14T00:07:18+00:00 Scott Moser smoser@ubuntu.com 2012-09-14T00:07:18+00:00 urn:sha1:18cbd9ae7872f83b4eaccdbdf2cf5023b92d7812 only emit if there is a device present. 2012-09-14T00:02:37+00:00 Scott Moser smoser@ubuntu.com 2012-09-14T00:02:37+00:00 urn:sha1:d2f00fd2af9417a91c78e9cab5747cd6e218aa39 add cloud-init-container.conf 2012-09-13T18:01:04+00:00 Scott Moser smoser@ubuntu.com 2012-09-13T18:01:04+00:00 urn:sha1:67bf7722398278e7089098dfd683389ef4e418c5 This changes the way that we avoid cloud-init-nonet hanging in a container. Previously, under LP: #800824 we tried 'start networking', but that caused issues described in LP: #1031065. Here, we emit the net-device-added for any devices that have not yet been seen. LP: #1031065