[01:06] Hi guys. i'm trying to boot coreos in a rather braindead enviroment that doesn't allow me to add a config-drive. I *do* have access to the filesystem image that I deploy, so I guess I could specify a URL or something and make cloud-init use that. But I don't know how to do that [01:06] So my question is how to manipulate the image so that it goes and looks for a cloud-init someplace else === zz_natorious is now known as natorious === natorious is now known as zz_natorious === zz_natorious is now known as natorious [14:22] smoser, Odd_Bloke I guess there's no meeting today? [16:19] murphyslawbbs: CoreOS uses their own homebrew version of cloud-init. Perhaps try and hit up their support channels? [16:25] ok ty [16:50] claudiupopa: I won't be at it, for sure. [16:50] At LinuxCon. :) === natorious is now known as zz_natorious === zz_natorious is now known as natorious [17:45] Oh, nice, enjoy. :-) === natorious is now known as zz_natorious === zz_natorious is now known as natorious [18:02] Hello, I am trying to add a repo to my cloud init file and it never actually adds it. I cant find anything helpful in the cloud init logs on the instance either. Can anyone see an issue? http://pastebin.com/jSpjGMkQ [18:02] The repo file just never shows up in /etc/yum.repos.d === natorious is now known as zz_natorious === zz_natorious is now known as natorious === natorious is now known as zz_natorious