| === meena8 is now known as meena | ||
| liyi | Is there anyway to run cloud init after the linux install? I have some cloud init script where I usually attach with aws ec2 launch but I would like to use it to setup my own linux desktop. | 17:50 |
|---|---|---|
| liyi | something like this(https://raw.githubusercontent.com/liyihuang/liyi-cloudinit/main/cloud-init.yaml) | 17:50 |
| minimal | liyi: what do you mean "after the linux install"? Normally cloud-init is used/enabled in pre-prepared Linux disk images, rather than during installations | 17:58 |
| minimal | oh, they only stayed in channel for 5mins lol | 18:02 |
| rharper | minimal: at least on ubuntu-server installs, it uses cloud-init on initial boot to handle first-time setup of things collected during install phase (like user names, gcos , ssh keys, etc); not sure about desktop though; https://discourse.ubuntu.com/t/automated-server-installation/16612 | 22:07 |
| minimal | rharper: yeah I wasn't referring to the likes of subquity etc | 22:38 |
| rharper | right, but I think liyi may have been asking if one could use cloud-init to customize a desktop install; I *think* that's coming with the subiquity-ifcation of the desktop installer but not 100% sure; | 22:41 |
| minimal | rharper: his repo has user-data for setting up k8s, I assumed he wanted to do similar to setup desktop but he did say "anyway to run cloud init after the linux install" which made me assume he wasn't using subiquity and instead was installing some distro and *then* wanting to install & use to setup desktop (i.e. as an alternative to ansible/salt/chef/puppet) | 23:05 |
| minimal | s/use /use cloud-init / | 23:05 |
| rharper | heh, yeah and they leave so quickly no way to follow up =/ | 23:08 |
| minimal | indeed | 23:10 |
| minimal | I must get around to writing that telepathy module for cloud-init ;-) | 23:11 |
| rharper | lol | 23:12 |
| minimal | I bet you didn't see that coming lol | 23:13 |
| rharper | hehe | 23:33 |
| meena | holmanb, falcojr: is https://github.com/canonical/cloud-init/pull/4769 supposed to work in general? everywhere I've tried it, it didn't. though I did hear it works in parallels | 23:41 |
| -ubottu:#cloud-init- Pull 4769 in canonical/cloud-init "feat: prefer udev's cdrom_id -e to eject" [Open] | 23:41 | |
| catred | meena: what is working/not working for you? In most of our testing the eject condition hasn't actually been being hit so if you're seeing failures that would be very helpful. | 23:57 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!