2024-07-19 21:40:39 Is zlib 1.3.1-r0 vulnerable to the CloudFlare issue (CVE-2023-6992)? I had thought Alpine's zlib was built from the upstream sources. 2024-07-20 16:33:35 So, I'm using generic_alpine-3.20.1-x86_64-bios-cloudinit-r0.qcow2 on Openstack 2024.1 -- Cloud-init is having issues contacting the metadata service , here is the console log from the box, I've tested over distros (Ubuntu, Kali, FreeBSD all work) https://paste.debian.net/1323817/ 2024-07-20 16:56:14 Looks like Alpine Cloud-init is not setting the metadata route it needs for link local access, it should be setting 169.254.169.254 | 100.64.1.1 | 255.255.255.255 2024-07-22 15:39:48 alpine 3.20.2 is released 2024-07-22 17:28:14 will start firing up the cloud image builds... 2024-07-22 17:39:04 im about to do 3 more stable releases for 3.19, 3.18 and 3.17 as well 2024-07-22 18:19:14 ncopa that was my next question 2024-07-22 18:35:57 they are all tagged now. thanks! 2024-07-22 18:55:50 builder not picking up the new 3.1[987]'s yet, maybe there's some other stuff building or metadata hasn't been pushed yet? 2024-07-22 18:57:03 ah metadata is missing 2024-07-22 18:59:08 should be there now 2024-07-22 19:09:56 👍 2024-07-23 21:10:37 https://alpinelinux.org/cloud should be updated with the latest cloud images 2024-07-24 06:38:31 awesome! thanks! 2024-07-25 17:46:50 tomalok: we need refactor the Makefile. We need to install the autodetect scripts with execute permissions, and we need to install incus 2024-07-25 17:47:08 not sure if it makes sense to have different install targets per cloud provider 2024-07-25 17:47:58 i think in the long run we want install all of them, and autodetect, so we can have a generic image for all(?) clouds 2024-07-25 18:11:38 the original idea was to only install what was necessary for each cloud -- a `generic` cloud APK would have dependencies on the other clouds 2024-07-25 18:12:19 also iirc, we haven't released new tiny-cloud APKs with the new stuff yet, either. 2024-07-25 18:12:34 i think thats fine, its a bit broken 2024-07-25 18:12:54 i have just created two MRs with the fixes. Im testing if they actually solves things 2024-07-25 18:13:05 im using distrobuilder and incus to test things 2024-07-25 18:13:05 AWS probably can't be "generic" either -- there are kernel commandline differneces 2024-07-25 18:13:12 ok 2024-07-25 18:13:24 i suppose nocloud and incus can be generic at least 2024-07-25 18:14:39 there may be similarities for other clouds too... just a question on how to autodetect them. dmidecode can detect AWS pre-network, but didn't have similar luck with OCI (didn't check gcp/azure)... 2024-07-25 18:15:22 i saw some larger doc on how to autodetect aws. 2024-07-25 18:16:51 ok. i can confirm that https://gitlab.alpinelinux.org/alpine/cloud/tiny-cloud/-/merge_requests/115 and https://gitlab.alpinelinux.org/alpine/cloud/tiny-cloud/-/merge_requests/116 works. 2024-07-25 18:16:56 with incus 2024-07-25 18:17:36 i get a couple of errors during boot though 2024-07-25 18:17:39 open: No such file or directory while opening /dev/mapper/vg0-lv_root 2024-07-25 18:17:39 ++ expand_root: starting 2024-07-25 18:17:39 resize2fs 1.47.0 (5-Feb-2023) 2024-07-25 18:17:39 ++ expand_root: failed 2024-07-25 18:18:27 which isnt really is an error. there is no root device that needs to be resized in an incus/lxc/lxd system container 2024-07-25 18:18:51 bit it boots up and reads the user-data 2024-07-25 18:19:57 i think there was an old issue about figuring out if LVM could be supported... but sounds like it's just trying to do the expand on the partition outside of the container 2024-07-25 18:20:20 that is what it is 2024-07-25 18:20:46 and the root partition is not exposed for the container, for natural reasons 2024-07-25 18:21:20 will try to take a peek at these MRs soonish... 2024-07-25 18:21:22 i dont know if we want disable expand root for incus, as you can create and run real VMs with incus as well 2024-07-25 18:22:26 as long as the error doesn't kill the rest of everything else, should be ok to leave it -- otherwise we can maybe make that nonfatal so it proceeds with other stuff after it 2024-07-25 18:23:13 it seems like it continues. the tiny-cloud-boot service fails though 2024-07-25 18:24:31 after that I'd like to look if we could make #cloud-config user-data handler an alias of #alpine-config 2024-07-25 18:24:56 virt-install has an option to pass ssh keys, and it creates #cloud-config yaml 2024-07-25 18:25:22 woudl be nice if that worked out of the box with tiny-cloud, which currently don't have any #cloud-config handler 2024-07-25 18:41:29 is what's in #alpine-config currently 100% compatible with #cloud-config? 2024-07-25 18:42:59 or does it add some things that cloud-config doesn't do? 2024-07-25 18:44:24 its not 100% compatible 2024-07-25 18:44:36 the format for apk packages is not supported by cloud-init 2024-07-25 18:44:50 i'd like to fix that in cloud-init though 2024-07-25 18:45:06 but that is very alpine specific though 2024-07-25 18:55:45 other option I have been thinking of is to move everything that is compatible with cloud-init to a cloud-config handler and let everythign that is not be in a separate alpine-config, which would simply source/extend the cloud-config 2024-07-25 19:18:14 wasn't there some apk/alpine additions to cloud-init -- or maybe there was a patch that wasn't merged? 2024-07-26 06:47:24 there are some apk additions to cloud-init, but I think they could be improved