[01:14] <dave_garvey> Thanks Chad, done
=== Guest44454 is now known as ice10001
[03:15] <ice10001> Any active users here?
[03:43] <ice10001> Finally downloaded a client so I can keep track and stay somewhat relevant on topic
[08:00] <benni> Im trying to run cloud-init with Ubuntu 22.04 and the NoCloud datasource. I created an ISO (9660) image (contains user-data and meta-data files) with label "cidata" and attached it to my vm. But the drive is not beeing found by cloud-init on startup. Do i have to mount the drive already in my vm-template?
[08:04] <benni> Im using a self-made cloud-init image based on an fresh Ubuntu 22.04 install. I executed "cloud-init clean" removed the files in /etc/cloud/cloud.cfg.d and added "NoCloud" to the datasource list in /etc/cloud/cloud.cfg.
[08:05] <benni> On boot it searches for an NoCloud Datasource but didnt find it.
=== fowl5 is now known as fowl
[15:00] <holmanb> iveskim: this is a starting point for contributing -> https://cloudinit.readthedocs.io/en/latest/topics/contributing.html
[15:03] <holmanb> ice10001: what's your config so far?
[15:07] <holmanb> benni: what virtualization method? does ds-identify identify the system as NoCloud? Could you share logs of the failed attempt?
[15:27] <blackboxsw> When I see the text "based on an fresh Ubuntu 22.04 install. " It makes me think benni used to live-server installer, which will leave the NoCloud seed file /etc/cloud-init/cloud.cfg.d/99-installer.cfg which also happens to provide `datasource_list: [NoCloud]` which limis what cloud-init can detect across next boot regardless of cloud-init clean. 
[15:27] <blackboxsw> ^ This is one of the rough edges in reuse of live-server installs that needs to be worked this cycle 
[15:28] <blackboxsw> we need cloud-init clean to be informed of what live-server config artifacts were installed if we want folks to be able to reuse/redeploy with these images
[19:44] <ice10001> Good morning all, @holmanb here is my config:
[19:46] <ice10001> https://pastebin.com/GgdZL7gu
[19:47] <ice10001> I have progressed by removing the $RELEASE from the source and manually added focal-pgdg main
[19:48] <ice10001> This does work, however, I was wanting the source to be generic to use the latest repo & install the latest postgresql-client (at the time)
[19:49] <ice10001> Behind that, I also want to add docker
[20:10] <ice10001> When I change the source to: "source: deb http://apt.postgresql.org/pub/repos/apt $(lsb_release -cs)-pgdg main" as per the postgresql site, my install completes but when I run sudo apt update, I get the following error:
[20:10] <ice10001> N: Updating from such a repository can't be done securely, and is therefore disabled by default.
[20:10] <ice10001> N: See apt-secure(8) manpage for repository creation and user configuration details.
[20:11] <ice10001> This appears before the above ^: E: The repository 'http://apt.postgresql.org/pub/repos/apt $(lsb_release Release' does not have a Release file.
[20:11] <ice10001> There is obvisouly a error @ 'http://apt.postgresql.org/pub/repos/apt $(lsb_release Release'
[20:47] <ice10001> I have fixed this, the correct format is: "source: deb http://apt.postgresql.org/pub/repos/apt $RELEASE-pgdg main" No spaces between $RELEASE and -pgdg
[20:47] <ice10001> Wish me luck on the docker stuff now.....