=== eb3095_ is now known as eb3095
=== andrewbogott_ is now known as andrewbogott
=== andrewbogott is now known as Guest3286
=== Guest3286 is now known as andrewbogott
=== andrewbogott is now known as Guest6120
=== Guest6120 is now known as andrewbogott
=== Guest6708 is now known as Daniel
=== esv_ is now known as esv
=== cpaelzer_ is now known as cpaelzer
[15:22] <falcojr> EugenMayer: I'm not sure what you mean by "via cloud-init itself". Modules should all run on first boot. The modules that are run are defined in /etc/cloud/cloud.cfg
[15:48] <EugenMayer> falcojr debian-generic-cloud does for examle not include the resolv_conf module, thus it wont run ( /etc/cloud/cloud.conf )
[15:49] <EugenMayer> My question is if there is something to enable cloud init modules
[15:53] <falcojr> ahh, you can "unverified_modules" in /etc/cloud/cloud.cfg
[15:53] <falcojr> https://github.com/canonical/cloud-init/blob/main/doc/examples/cloud-config.txt#L183
[15:55] <EugenMayer> falcojr wait are you telling me that the list of modules is not determined / set by debian maintainers explicitly but implicitly deactivated due to sanity checks on boot?
[16:04] <minimal> EugenMayer: some modules are only supported on some OSes/distros
[16:19] <EugenMayer> interesting, and resolv_conf is one of those?
=== gschanuel1 is now known as gschanuel
[16:39] <minimal> EugenMayer: if you look at cc_resolv_conf.py it states: "**Supported distros:** alpine, fedora, photon, rhel, sles"
[18:07] <EugenMayer> minimal did not look into that, but thank you big times for the information!
[18:08] <minimal> EugenMayer: typically Debian would be using resolverconf to manage /etc/resolv.conf so that's why c-i resolv_conf is not expected to be used/supported