2024-09-06 11:35:45 <ncopa> heads up: I'm tagging new stable releases!
2024-09-06 12:30:11 <ncopa> tomalok: new stable releases are out
2024-09-06 13:30:37 <tomalok> ncopa: rgr, will start the cloud build soon
2024-09-07 14:34:11 <tomalok> ikke: the new images should be staged for release to CDN, will have a MR later for updating the alpinelinux.org/cloud
2024-09-07 14:34:23 <ikke> alright, will trigger the sync
2024-09-07 18:24:12 <ikke> everything is synced
2024-09-07 18:41:23 <tomalok> ikke https://gitlab.alpinelinux.org/alpine/infra/alpine-mksite/-/merge_requests/86
2024-09-07 18:55:27 <ikke> tomalok: pushed to production
2024-09-07 19:46:25 <tomalok> ikke: 👍
2024-09-09 06:08:39 <ncopa> thanks!
2024-09-16 20:34:22 <durrendal> hello dhruvin 
2024-09-16 20:34:36 <dhruvin> durrendal In case of custom images, I'm afraid you won't be able to use do-agent just yet.
2024-09-16 20:35:05 <dhruvin> I'm checking if they added support for advanced metrics in custom images.
2024-09-16 20:38:35 <dhruvin> Currently, I wipe a debian instance and install alpine onto it. That way, I get ipv6 and advanced metrics support.
2024-09-16 20:45:23 <durrendal> ah that's a shame, though I'm not surprised. the custom image support has always been an ad hoc sort of solution
2024-09-16 20:46:08 <durrendal> the wipe and reinstall method isn't hard though, I might consider doing that. Having additional metrics and ipv6 is nice. I can live without both
2024-09-16 20:46:18 <durrendal> but I could have both too, so that's tempting
2024-09-16 20:49:38 <dhruvin> Did we stop offering qcow2 images in Virtual section of https://alpinelinux.org/downloads/? Or am I misremembering?
2024-09-16 20:53:14 <dhruvin> durrendal: Adding support for configdrive to tiny-cloud could ease deploying alpine to digital ocean. But still, ipv6 and metrics will remain missing. It's more of a DigitalOcean issue, and less of a cloud-init/tiny-cloud issue.
2024-09-16 21:07:40 <dhruvin> > Monitoring is not supported for this configuration, please try a different region or distribution.
2024-09-16 21:09:13 <dhruvin> DO indeed doesn't offer advanced metrics support for instanced with custom images. Not in SGP for a $4 machine.
2024-09-16 21:09:30 <dhruvin> *instances
2024-09-16 21:12:21 <dhruvin> Anyhow, feel free to tag me here or on gitlab, if you run do-agent and encounter any issues with it.
2024-09-17 00:41:07 <tomalok> durrendal / dhruvin - others have submitted MRs to tiny-cloud to get it working on other cloud providers
2024-09-17 02:02:55 <ikke> dhruvin: did you check https://alpinelinux.org/cloud/?
2024-09-17 11:55:32 <dhruvin> Yes, I missed it.
2024-09-17 13:18:49 <durrendal> yeah it does seem to be a bit of a digital ocean image, it would be nice if they carried an official alpine image that worked out the box
2024-09-17 13:19:02 <durrendal> but that's okay. I'll definitely give do-agent and go and let you know if any issues arise ^^
2024-09-26 16:23:34 <dovsienko> hello all. I tried a few Alpine 3.20.3 images for VMs (both BIOS and UEFI) on Digital Ocean and they don't boot beyond printing the very first few messages (kernel/initrd on BIOS and "booting from disk 0" on UEFI)
2024-09-26 16:24:23 <dovsienko> there are various scripts published by various people to cook a DIY Alpine disk image, is that the only way to get it to run there? Alpine works in my VirtualBox fine
2024-09-26 16:26:55 <ncopa> does not look like we build images for digital ocean
2024-09-26 16:26:56 <dovsienko> also I have another Alpine VM on AArch64 and it runs fine, so it would be interesting to understand what the problem is
2024-09-26 16:26:57 <ncopa> https://gitlab.alpinelinux.org/alpine/cloud/tiny-cloud/-/tree/main/lib/tiny-cloud/cloud?ref_type=heads
2024-09-26 16:28:00 <dovsienko> I tried "generic" and "nocloud" but did not see any difference
2024-09-26 16:29:05 <dovsienko> FWIW, FreeBSD and OpenBSD run OK on Digital Ocean, so I hoped to see the boot process starting and progressing to some extent
2024-09-26 16:29:42 <ikke> Maybe DO requires some specific drivers
2024-09-26 16:30:43 <dovsienko> is there an easy way to enable the usual kernel boot progress messages to see where it breaks (not finding the root filesystem device etc)
2024-09-26 16:30:52 <dovsienko> s/hot/not/
2024-09-26 16:31:02 <dovsienko> ?
2024-09-26 16:31:22 <ikke> Oh, does it perhaps requires the kernel to output on some serial device?
2024-09-26 16:31:33 <dovsienko> for reference, NetBSD also fails to boot on DO
2024-09-26 16:32:16 <dovsienko> I do not know. the boot screen shows SeaBIOS at the top
2024-09-26 16:34:04 <ikke> dovsienko: from a running VM, can you check the output of /proc/cmdline
2024-09-26 16:35:31 <ncopa> dovsienko: which image did you try? the nocloud cloudinit ?
2024-09-26 16:35:50 <dovsienko> BOOT_IMAGE=/boot/vmlinuz-6.1.0-25-amd64 root=PARTUUID=d5826239-67ad-4bc0-9d89-969e153356dc ro console=tty0 console=ttyS0,115200 earlyprintk=ttyS0,115200 consoleblank=0 net.ifnames=0 biosdevname=0
2024-09-26 16:36:03 <dovsienko> (that's from Debian 12 as installed by DO)
2024-09-26 16:36:19 <ikke> console=tty0 console=ttyS0,115200 earlyprintk=ttyS0,115200
2024-09-26 16:36:46 <ikke> But I don't think you even get to the point where you could modify the kernel cmdline, do you?
2024-09-26 16:37:57 <dovsienko> generic_alpine-3.20.3-x86_64-bios-cloudinit-r0.qcow2, nocloud_alpine-3.20.3-x86_64-bios-cloudinit-r0.qcow2 and generic_alpine-3.20.3-x86_64-uefi-cloudinit-r0.qcow2 (then ran out of patience)
2024-09-26 16:38:25 <ncopa> i would guess generic cloudinit vm should be the best option
2024-09-26 16:38:47 <dovsienko> yes, except it does not boot
2024-09-26 16:39:29 <dovsienko> so before trying the various DIY image recipes I thought maybe this is a known problem and decided to ask
2024-09-26 16:40:40 <ncopa> never tried it, but I would be interested in hearing why it fails, if you figure it out
2024-09-26 16:40:56 <dovsienko> do not worry about it too much though: the main reason I would like to run Alpine is to test-compile software on a musl system, and I can do that in the AArch64 VM without much difficulty
2024-09-26 16:42:42 <ikke> https://github.com/benpye/alpine-droplet seems to use https://github.com/alpinelinux/alpine-make-vm-image/
2024-09-26 16:44:41 <ikke> dovsienko: did you try a non-cloud image?
2024-09-26 16:49:13 <dovsienko> meanwhile I have just tried logging into the FreeBSD console and got a login failure on ttyv0, which indicates this type of VM uses the usual (non-serial) console (although FreeBSD boot log says it uses serial port as a secondary console)
2024-09-26 16:49:50 <dovsienko> so this leads me to think the lack of boot messages is not caused by the boot process switching from a serial console to a VGA console
2024-09-26 16:50:36 <dovsienko> ikke: yes, there are a few different ones
2024-09-26 16:51:26 <dovsienko> ikke: the non-cloud ones are either .iso or a root filesystem tarball (there's one script that uses the latter to replace a pre-installed VM)
2024-09-26 16:52:18 <dovsienko> I could install a VM from an .iso in VirtualBox and then use the disk image to create a DO VM, if it helps
2024-09-26 16:58:41 <dovsienko> for reference, OmniOS also fails to boot on DO
2024-09-26 17:29:56 <durrendal> dovsienko: for what it's worth, I've used the alpine-make-vm-image script in the past to launch Alpine images on DO. It works well.
2024-09-26 17:30:47 <durrendal> https://github.com/alpinelinux/alpine-make-vm-image/blob/master/alpine-make-vm-image#L644 <- it does modify the boot setup for the image it creates. But it's not something super special just a simple UEFI boot or extlinux config https://github.com/alpinelinux/alpine-make-vm-image/blob/master/alpine-make-vm-image#L624
2024-09-26 17:31:55 <durrendal> I would go the route of using the available tooling to create a bootable DO image, and just boot from that. If you need/want to use the data dashboards then you'd need to install alpine over one of their images though
2024-09-26 17:32:47 <durrendal> like a debian or ubuntu base. If you don't do that then you can't use static IP addresses or their cloudwatch offering, whatever it is that they call it. I can never remember any of the terms outside whatever AWS has drilled into my head
2024-09-26 17:33:21 <dovsienko> durrendal: thank you for the advice. do you mean the CPU/disk/RAM graphs? they work in FreeBSD and OpenBSD
2024-09-26 17:33:43 <dovsienko> (or rather _for_ FreeBSD and OpenBSD VMs)
2024-09-26 17:35:24 <durrendal> no those should work fine with the DIY image. I meant if you needed to use their in console alerting/metric systems via the do-agent
2024-09-26 17:35:26 <durrendal> https://github.com/digitalocean/do-agent