2025-12-02 15:45:58 i wonder if it would make sense to have a nocloud image for raspberry pi, with the linux-rpi kernel 2025-12-02 15:46:36 we currently have an rpi image that is a "diskless" live image, with FAT 2025-12-02 15:46:53 but I think rpi users expect it to be a runable pre installed filesystem 2025-12-03 01:47:08 hm, that'd add a new arch to the mix, it's doable but unless someone's waiting for it, maybe after more cloud image consolidation happens to save some space on the CDN 2025-12-03 16:55:46 ok 2025-12-03 16:55:54 alpine 3.23.0 was released 2025-12-03 18:04:09 i'll start the cloud image building later today 2025-12-03 18:04:56 ack 2025-12-03 18:05:08 tomalok: What is your stance about retention for cloud images? 2025-12-03 18:07:48 with regards to CDN or having them published to AWS? 2025-12-03 18:08:05 CDN 2025-12-03 18:08:48 what's the policy for the non-cloud images? 2025-12-03 18:09:22 it's nice to see the long history, but it also takes up valuable space 2025-12-03 18:11:06 as long as old packages / base image are still available it should be possible to re-assemble older releases 2025-12-03 18:11:15 (if there's a request to do so) 2025-12-03 18:11:27 Ideweally we would be able to archive them at least 2025-12-03 18:11:32 Ideally* 2025-12-03 18:13:22 personally i'm fine to drop after it falls off the end of any type of support... so 3.23, 3.22, 3.21, 3.20 -- and after that go to the archives 2025-12-07 11:30:33 so - the latest cloud image on GCP.... It seems that the cloud-init image didn't install SSH keys 2025-12-07 11:30:37 but the tiny one did. 2025-12-07 11:31:03 hours of ripping my hair out at the stupid tools Google give you lol 2025-12-07 11:31:13 the tiny one worked first time 2025-12-07 15:32:11 CRCinAU - currently, the behavior of Tiny Cloud is actually incorrect. It should only install the SSH keys for the specified user login, instead of all of those. GCP figures out what login the key is for from the comment field of each key. 2025-12-07 15:33:06 so if you want the key to be installed for the default "alpine" login, the key must be something like "ssh-rsa key-stuff-here alpine" 2025-12-07 15:34:22 (this is for ssh keys defined for the project and instance, at instantiation time.) 2025-12-07 23:20:34 yeah - that didn't work using cloud-init at all 2025-12-07 23:20:39 none of the SSH keys got installed. 2025-12-07 23:20:58 however, tiny did install the SSH key into the alpine user - which was enough to get in at least 2025-12-08 01:11:27 fwiw - I didn't use any special data - just the bog standard SSH keys in the GCP management. 2025-12-08 02:17:34 when launching a GCP instance from the web console, at the bottom of the "Security" tab, click "Manage Access" and then "+ Add Item" under manually generated SSH keys? 2025-12-08 02:28:44 Yeah - I did that - but with global keys aka project wide. 2025-12-08 02:28:51 the cloud-init still didn't grab them. 2025-12-08 02:29:13 but the tiny did - alas for the alpine user, not the username at the end of the key. 2025-12-08 02:29:25 however, at least that worked enough for me to get access and fix those properly 2025-12-08 02:34:19 just launched a cloud-init image -- keys that had "alpine" or "alpine@foo.com" were installed in ~alpine/.ssh/authorized keys -- those with a blank or other login/email in the comment field were skipped... if i read the above correctly you were using project-wide ssh keys? that i didn't test 2025-12-08 02:34:47 ...cloudinit, but i know tiny-cloud does grab those 2025-12-08 02:35:03 I'm pretty sure I had 'alpine' at the end...... but yeah, only project wide for this one. 2025-12-08 02:35:22 I don't do these things often, so like this is the first time I've done a new GCP VM in like...... 3-4 years? 2025-12-08 02:35:40 I even tried to just mount the disk image in another temporary VM - but everything was screwed up then 2025-12-08 02:35:43 no idea why 2025-12-08 02:36:06 but if I just do `fdisk -l /dev/sda`, then the partition table looks like garbage. 2025-12-08 02:36:15 let me see if i can find where project keys are 2025-12-08 02:36:24 I'm wondering if its GPT partition table that fdisk can't understand 2025-12-08 02:36:49 but I mean, it boots.... so something is working 2025-12-08 02:36:53 if it's uefi image, it's GPT partition table, iirc 2025-12-08 02:37:20 I couldn't get the UEFI one to boot either 2025-12-08 02:37:33 it kept coming back with sebios issues - so I used the normal BIOS image 2025-12-08 02:38:19 ie when I connected to the serial console, it kept bootlooping with sebios issues 2025-12-08 02:38:25 wait - seabios? 2025-12-08 02:38:58 yeah - seabios. No matter what I tried I couldn't get it to use a UEFI image 2025-12-08 02:39:35 which is weird, as I thought that things like GCP would prefer UEFI (probably OVMF?) over seabios 2025-12-08 02:41:17 when the images are imported, you select whether they're UEFI or not -- https://gitlab.alpinelinux.org/alpine/cloud/alpine-cloud-images/-/blob/main/IMPORTING.md?ref_type=heads#gcp 2025-12-08 02:41:59 oh - I did it all via the web UI 2025-12-08 02:43:31 i had problems with web ui, though it's been a while since i tried 2025-12-08 02:43:55 yeah it was ..... an experience :P 2025-12-08 02:44:11 makes me realise how much I like proxmox hahahahah 2025-12-08 02:44:25 but hey - this was for a free e2.micro to do secondary DNS 2025-12-08 02:44:52 so the price is right..... I used Fedora before - but its a little to heavy for 2 vCPUs + 1Gb RAM 2025-12-08 02:47:12 just verified that cloud-init also respects project ssh keys -- if they've got the "alpine" user in the comment 2025-12-08 02:47:59 huh - maybe I made an error on that one. 2025-12-08 02:48:38 it took me a *lot* of trial and error - but maybe when I redid everything I got that part wrong 2025-12-08 02:49:41 I do have a project-wide key in there atm that is *not* for the alpine user. 2025-12-08 02:50:21 do I need to care about the BIOS vs UEFI boot? 2025-12-08 02:56:22 shouldn't need to care, as long as you tagged the image correctly when importing 2025-12-08 02:59:07 now I'm just trying to remember where to set the DNS PTR for the public ip lol 2025-12-08 03:02:37 eyyyy there we go lol 2025-12-08 03:04:08 I was thinking of doing a BYO IP space :D 2025-12-08 03:04:25 but then I'd likely have to end up paying for VMs etc. 2025-12-08 03:04:34 so the free tier is fine for a DNS server 2025-12-08 20:51:04 thanks for publishing 3.23 on aws ec2! 2025-12-08 21:46:49 thresh not fully released just yet, but if you find it in a region it's useable. 2025-12-08 21:52:04 tomalok, yeah seems like the region I use has both amd64 and aarch64; was able to bake a golden image for my needs w/o any issues 2025-12-08 23:21:35 there are a couple regions that can't be published to until we delete the EOL images, and the downloadable images (also for non-AWS) still needs to be syncd to CDN 2025-12-09 08:28:04 tomalok: The directory has been created 2025-12-09 14:46:40 ikke: thx! 2025-12-09 15:42:04 ikke: should be ready to sync out now 2025-12-09 20:11:29 ikke: https://gitlab.alpinelinux.org/alpine/infra/alpine-mksite/-/merge_requests/117 (finally!) 2025-12-10 15:08:44 tomalok: files have been synchronized 2025-12-10 15:33:10 ikke: thanks! 2025-12-13 15:30:58 ikke: looks like that MR is still pending to update the https://alpinelinux.org/cloud site yet? 2025-12-14 05:03:09 Sorry, I'm traveling atm, but it has been pushed now 2025-12-14 21:33:17 ikke ah, i know what that's like... thank you!