2021-08-05 14:26:32 hi 2021-08-05 14:26:44 im have tagged alpine 3.14.1 now 2021-08-07 03:36:35 thanks, ncopa. I'm just back from vacation, starting the AMI builds now 2021-08-07 05:27:37 ncopa, ikke: should be all set to rebuild https://alpinelinux.org/cloud 2021-08-07 06:19:47 tomalok: done 2021-08-07 13:15:15 Hi! A question about cloid-init in the standard apline linux aws image: cloud-init is not installed by default, right? What is the recommended way to pass any commands inside a alpine linux aws machine? 2021-08-07 16:34:59 igor_: you can pass a shell script as user_data when launching the instance 2021-08-07 16:35:27 https://github.com/mcrute/tiny-ec2-bootstrap 2021-08-07 16:38:06 we're (slowly) working on expanding the flavors of images available -- bootstrap is one of those dimensions (tiny-ec2-bootstrap vs. cloud-init) 2021-08-07 16:38:26 ikka: thx! 2021-08-07 18:33:13 igor_: If you're interested in cloud-init you might want to have a look at my script for creating cloud-init enabled Alpine images: https://github.com/dermotbradley/create-alpine-disk-image 2021-08-07 18:35:53 igor_: the "missing" README.Alpine you mention in #alpine-linux is in the cloud-init-doc package. I'm the cloud-init maintainer :-) 2021-08-07 20:37:09 speaking of tiny-ec2-bootstrap/cloud-init, it needs to support `doas` 2021-08-07 20:37:29 https://gitlab.alpinelinux.org/alpine/tsc/-/issues/1 explains why 2021-08-07 20:54:15 cloud-init only really supports sudo currently - its not used to "run" cloud-init but rather cloud-init YAML files manage the creation of sudo config files for users 2021-08-07 20:55:31 to also support doas would require an upstream change in the (from memory) users_groups module. Of course that would rely on the proposed multiple config-file directory change for doas 2021-08-07 23:03:32 ariadne: looks like sudo use in alpine-ec2-ami is installed as an additional package just so the default user (alpine) can do stuff. (the build host also uses sudo for executing the setup script, but that wouldn't end up in the resulting image). tiny-ec2-bootstrap itself isn't using sudo. 2021-08-07 23:04:05 okay 2021-08-07 23:04:18 well, we plan to move forward on deprecation of sudo, by moving it to `community` :) 2021-08-07 23:04:49 yep, saw that fly by on the dev mailing list 2021-08-07 23:06:30 will need to brush up on doas details and see how that affects stuff downstream -- folks may be expecting to use sudo in their bootstrap userdata scripts 2021-08-07 23:07:14 (though that oneshot script already runs as root, anyway) 2021-08-07 23:36:06 ariadne: seem to be missing some secret sauce for doas installed on my lab box ... /etc/doas.conf _should_ be set to allow anyone in group wheel but i keep on getting "doas: Operation not permitted" 2021-08-07 23:37:08 is doas actually setuid :D 2021-08-07 23:39:00 🤦 just saw, current user isn't in group wheel. :P 2021-08-07 23:41:56 works much better when the user is in wheel ;) 2021-08-08 01:36:49 actually the issue with cloud-init re: sudo is that "sudo" is part of cloud-init's defined YAML grammar when creating users, its a way to specify sudo rule(s) for the relevant user. So unless code was written for cloud-init to translate sudo rule syntax into doas syntax then doas can't replace that. 2021-08-08 01:38:38 Separately I could work on an upstream MR to add a "doas" key to the YAML grammar (might be some interest from the BSD cloud-init people) buy that's not relevant to the use of the "sudo" key in existing YAML files out there (some of which may even be created by scripts/terraform/ansible etc) 2021-08-08 01:39:11 anyway as the Alpine cloud-init package is in community then its not affect by sudo moving from main to community 2021-08-08 06:38:19 tomalok: thank you for your answers; I wonder if cloud-init is not installed in the instance, then who executes the user-data script? Actually, that is the only reason why I need cloud-init: to execute my script. 2021-08-08 06:41:00 tomalok: Of course I understand that I can create my own image with everything needed (incl. cloud-init) installed in it, but I thought maybe something is available in the alpine-linux images out of the box, so that you can just take a standard image and pass your commands to it 2021-08-08 16:51:23 igor_: similar to cloud-init (but with its configuration), tiny-ec2-bootstrap has an init script that gets the script from the instance's user and executes it (and does a couple other things) on first boot -- it's less complicated and much smaller footprint than cloud-init. 2021-08-08 16:52:17 igor_: what sorts of things are you wanting cloud-init to set up for you? 2021-08-08 17:02:28 igor_: you could, in theory, also use the same builder we do with a custom profile to roll your own AMIs with the extra packages installed/uninstalled and services enabled/disabled -- i do this for my own personal AMIs... but there is some detangling that needs to be done to cleanly move from tiny-ec2-bootstrap to cloud-init -- IIRC, the ENI 2021-08-08 17:02:28 (networking) config/hotplug stuff and EBS device aliasing, both of which have mdev hooks, wheras (again, IIRC) cloud-init uses (e?)udev instead. 2021-08-08 17:03:39 igor_: https://github.com/mcrute/alpine-ec2-ami has some documentation about rolling your own, mostly up to date, i think. 2021-08-08 17:18:18 minimal: cloud-init uses (e?)udev and not mdev? (confirming what i typed just before you logged back in) 2021-08-08 17:19:35 tomalok: yes it only supports udev 2021-08-08 17:20:03 udev is used for the persistent rules it creates for network devices and also for the disk-related module 2021-08-08 17:20:33 I have thought about adding mdev support to cloud-init but that's something for the future... 2021-08-08 17:22:38 tomalok: re hotplug, the next upstream release of cloud-init has some network hotplug support, I'm working on getting it working with Alpine 2021-08-08 17:24:30 also for "rolling your own" for cloud-init there's my script at https://github.com/dermotbradley/create-alpine-disk-image :-) 2021-08-08 17:26:12 minimal: cool, thanks for the update. i've got your github project bookmarked too, as i (slowly) sort out broadening the dimensions of what the alpine-cloud-image builder can build (hopefully without having to spin up in-cloud instances) 2021-08-08 17:27:40 tomalok: the hotplug stuff (in next release) is only currently implemented for EC2 and Openstack (from memory) but its a start. 2021-08-08 17:29:27 re: avoiding having to spin up cloud instances, most (but not) cloud providers provide a way to import prepared disk images. Unfortunately not all of them do - e.g. from memory Linode don't :-( 2021-08-08 17:54:22 minimal: re: linode requiring spin up of instance to make image -- one of the reasons why the cloud builder should support multiple packer build backends 2021-08-08 17:55:17 it'll be selected/defined in the "cloud" dimension for a cloud's build 2021-08-08 17:56:05 but should still be able to make use of generalized provisioners and post-procesors, as necessary 2021-08-08 17:58:37 obviously you're somewhat limited by the set of backends for Packer 2021-08-08 17:59:30 my point was whether using Packer or chroot (as my script does) to build a image, if you then want to get it onto a cloud provider some of those providers don't make life easy :-( 2021-08-08 17:59:58 i figure _most_ of the major clouds should be able to be built with the qemu backends 2021-08-08 18:00:15 s/backends/backend/ 2021-08-08 18:01:53 haven't taken a look at linode yet (there's a build backend for it) been "focused" on aws, oci, gcp, azure 2021-08-08 18:05:35 I've been bogged down getting encryption working for UEFI/BIOS Syslinux/Grub but intend to test Hetzner, Vultr, and AWS initially 2021-08-09 00:34:58 i dont think we need to worry about linode; they already support alpine 2021-08-09 03:21:29 with the all the build system changes on deck, just getting an AWS to build and import will probably be the first major hurdle 2021-08-09 03:23:00 then probably OCI (because Day Job), and then GCP/Azure to round out the big four 2021-08-09 03:23:44 after the first two are done, it should be clearer how to arbitrarily add more clouds. 2021-08-09 05:47:13 tomalok: No, I am perfectly fine with tine-ec2-bootstrap; I don't need the real cloud-init; the only thing that I need is "something" that will accept my user-data and execute it. Currently, I also use that feature if cloud-init, that the user-data is in YAML, and just add my own section to that YAML; in the sh-based user-data it won't be so nice, but it does not matter; I can just encode my config data as base64 2021-08-09 05:48:12 tomalok: The only thing that I need is some sort of an agent that will execute my user-data, and tiny-ec2-bootstrap could do it too, of course 2021-08-09 05:50:14 tomalok: But it is not installed in the default images either, right? So I need to build my own AMIs anyway? That's exactly what I would like to avoid, because though I can build the images during the development phase, I would like to use some standard images when rolling out the software, because it must run in all regions etc 2021-08-09 05:51:32 tomalok: Currently I use ubuntu + cloud-init for that, and this approach works perfectly fine, with the only single problem, that ubuntu is too bloated, and I would like to switch to alpine 2021-08-09 05:58:03 tomalok: stop! Now I see that tiny-ec2-bootstrap is there by default! Very good! That's what I need. I can go with it, and actually I don't really nneed cloud-init then. Sure, it has some advantages like support of other clouds (azure, gcp, openstack), but maybe in future tiny-ec2-bootstrap will have them too 2021-08-09 15:46:53 igor_: The AMIs you'll find at https://alpinelinux.org/cloud/ all have tiny-ec2-bootstrap installed and enabled. 2021-08-09 15:48:05 (as i now read further with my half-asleep brain, that you've already discovered) 2021-08-15 14:57:09 Hi all 2021-08-15 15:01:30 I found a wiki: Replacing Non-Alpine_Linux_with_Alpine remotely, but it clearly says "physical server", someone would be so kind to guide me to achieve it but on azure 2021-08-15 15:06:52 I mean, is it safe to try on a virtual machine (azure), I would like not to format the whole physical server and affect third parties! jojojoj! 2021-08-15 16:35:31 hello, my pc was suspended, I did not know if someone answered about alpine in azure, thanks. 2021-08-15 16:35:47 not yet 2021-08-15 16:36:41 joseAlvarez: link to that wiki? 2021-08-15 16:37:13 yes 2021-08-15 16:37:33 https://wiki.alpinelinux.org/wiki/Replacing_non-Alpine_Linux_with_Alpine_remotely 2021-08-15 16:39:10 you could try to set up an azure vm that you don't mind destroying and see how it goes? 2021-08-15 16:40:14 fwiw, i'm working on expanding the breadth and depth of alpine images for clouds -- but no ETA at the moment 2021-08-15 16:41:11 Yes, with pleasure. 2021-08-15 16:43:11 I'll use alpine-virt-3.14.1-x86_64.iso 2021-08-15 16:49:50 joseAlvarez: why do you want to replace ubuntu on an Azure VM, why not create a new VM using Alpine? 2021-08-15 16:50:19 minimal: they mentioned that azure does not offer Alpine Linux 2021-08-15 16:50:55 ikke: right, but that's a different issue than deciding to replace an OS. 2021-08-15 16:51:19 It's another strategy: deploy one OS, and pivot to another 2021-08-15 16:52:00 my alpine script does, in theory, creates an alpine cloud-init image for Azure but I've never actually tested it as I've never used Azure yet 2021-08-15 16:52:37 ikke: ack, but its more messy switching OS 2021-08-15 16:53:04 minimal: sure, but if there is no other option? 2021-08-15 16:53:43 ikke: well if he was willing to work with me to test my script then I could address any Azure-specific issues to get it working 2021-08-15 17:01:49 he'd have to setup cloud-init anyway once he gets Alpine onto the machine so it would make sense to use an already prepped disk image in the first place 2021-08-15 17:44:29 hi, the experience was wonderful. as always. now I have Alpine on Azure I am very happy, thank you! I followed the steps using VNC 2021-08-15 17:57:13 joseAlvarez: not sure if you saw my earlier message but I have a script I'm working on for creating alpine cloud-init images for various Cloud providers. I haven't tested Azure yet but it should in theory work there. It would enable you to upload an Alpine image to Azure and create new VMs using that image 2021-08-15 17:57:56 have you installed cloud-init on the Alpine you have just setup? 2021-08-15 19:02:23 Hello minimal, I will gladly help you, tell me how. and no I have never used cloud-init. 2021-08-15 19:03:36 joseAlvarez: cloud-init is used by the majority of Cloud Providers so that during 1st boot of a VM the hostname/network config/timezone/etc can all be configured automatically 2021-08-15 19:04:23 its also used with Ubuntu for example, so when you created that VM I would expect cloud-init ran to set it up 2021-08-15 19:05:51 ok. lets doit 2021-08-15 19:06:27 My script is here: https://github.com/dermotbradley/create-alpine-disk-image 2021-08-15 19:07:19 I have written some note for Azure but (a) I've never tested them, and (b) they use some Azure CLI tools that are (not currently) ported to Alpine, though I assume they are available for Debian, Ubuntu, etc. The inof is here: https://github.com/dermotbradley/create-alpine-disk-image/blob/main/Cloud/Azure.md 2021-08-15 19:08:04 the basic idea is that you can run the script anywhere, e.g. on your local Linux computer, and then import the created disk image into Azure 2021-08-15 19:09:24 It's amazing, it would be great to be able to clone my current physical server to the cloud. 2021-08-15 19:14:55 Doesn't matter if I already install any packages? 2021-08-15 19:15:37 or should a clean install be preferable? 2021-08-15 19:19:06 the script is designed to create a complete OS disk image, so there's no actual "install" involved, once you have stored the disk image on Azure then you pick it when creating VMs 2021-08-15 19:21:06 this seems to be relevant: https://docs.microsoft.com/en-us/azure/virtual-machines/linux/upload-vhd 2021-08-15 19:32:42 azvpn:~# create-alpine-disk-image --cloud azure --script-filename create.sh 2021-08-15 19:32:44 -ash: create-alpine-disk-image: not found 2021-08-15 19:33:25 ./create-alpine-disk-image if its in the current directory 2021-08-15 19:34:42 I'm doing something wrong. first install cloud-init, then run setup-cloud-init 2021-08-15 19:34:50 ok -ash: ./create-alpine-disk-image: not found 2021-08-15 19:36:05 I haven't spelt out every last command as I'm assuming some basic Linux knowledge. Try "chmod +x create-alpine-disk-image" to make it executable 2021-08-16 17:55:51 hi guys 2021-08-16 17:56:43 it would be nice to get everyone interested in cloud stuff together for a meeting at some point, so we can kind of plan out what to do for 3.15/3.16 release cycles 2021-08-16 17:56:47 what do you think? 2021-08-16 19:35:22 Ariadne: yes I'm up for meeting 2021-08-16 19:45:44 Ariadne: yep, i'm up for that, too 2021-08-16 19:45:55 what about mcrute 2021-08-16 19:46:21 i did hear from mcrute over the weekend -- his irc notification stuff hasn't been working, but he's alive ;) 2021-08-16 19:46:43 okay. i'll mail everyone and we can find a time in say, two weeks? 2021-08-16 19:47:14 should be doable on my side. 2021-08-16 19:47:17 I'm in GMT/BST timezone but fairly flexible about times later in my day 2021-08-16 19:47:32 (fwiw, i'm US/Pacific) 2021-08-16 19:47:50 as is mcrute 2021-08-16 19:47:59 2 AM got it 2021-08-16 19:48:00 :P 2021-08-16 19:48:16 its always 2am somewhere :-) 2021-08-16 19:48:28 my "still up at 2am" days are sadly in the past... 2021-08-16 19:49:16 i'm a mix of US/Central and JST at the moment 2021-08-16 19:55:00 US/Pacific is UTC-8 isn't it, so 10am/11am/midday/1pm your time would be 6/7/8/9pm here which would be fine for me 2021-08-16 19:57:32 currently UTC-7... BST is currently... GMT-1? woulds still be 8h between us. 2021-08-16 19:59:01 GMT+1 2021-08-16 19:59:14 because math is hard... ;P 2021-08-16 20:23:18 please include me 2021-08-17 05:20:31 Ariadne: two weeks should work... I too am in PST (Seattle) 2021-08-17 05:21:05 also yeah my notifications are broken so I'm lagging on paying attention to IRC... really should fix that at some point :-) 2021-08-17 05:52:08 i dont have everyone's mails 2021-08-17 05:52:21 but i will get out a scheduling link once i do 2021-08-27 14:20:43 looks like I'll work on building 3.14.2 AMIs at some point today 2021-08-27 14:23:15 awesome! thanks! 2021-08-27 14:23:57 i think i need to add "notify cloud team" as the first checkbox in my release todo-list 2021-08-27 14:24:12 i should have given you a heads up 2021-08-27 15:42:17 as mcrute's moved alpine-ec2-ami repo over to alpine gitlab, i suspect the code that generates https://alpinelinux.org/cloud will need a slight update too 2021-08-27 15:44:19 and i might as well flip the edge AMI to use doas too, if that's going to be an official thing for 3.15 [ncopa, ariadne] 2021-08-27 15:44:42 ^^ ncopa ariadne 2021-08-27 15:51:46 tomalok: this should fix it: https://gitlab.alpinelinux.org/alpine/infra/alpine-mksite/-/blob/master/Makefile#L28 2021-08-27 15:52:12 I'll make the change if I have a chance this afternoon otherwise feel free to ping me on the MR, I have merge privs for the website IIRC 2021-08-27 15:52:25 but I've gotta run for now 2021-08-27 16:50:10 mcrute already found and patched in a branch :) 2021-08-27 16:51:38 but then the DayJob™ started taking precedence... 2021-08-27 17:05:56 https://gitlab.alpinelinux.org/alpine/infra/alpine-mksite/-/merge_requests/31 2021-08-27 17:06:46 update to alpine-ec2-ami for 3.14.2 still in the works 2021-08-27 18:42:50 okay, I did the review but I guess I can't merge... will need ncopa I think 2021-08-27 18:49:26 or perhaps ikke 2021-08-27 23:13:50 3.14.2 (and new edge) AMIs are built -- working on the push/release to all the regions 2021-08-28 00:10:26 https://gitlab.alpinelinux.org/alpine/cloud/alpine-ec2-ami/-/merge_requests/123 - it appears i have the power to merge in this repo... but posting this here if anyone wants to take a peek. 2021-08-28 00:11:55 new edge AMIs switch from sudo to doas which appears to work in my (limited) testing. 2021-08-28 15:07:32 thanks for the alpine/infra/alpine-mksite!31 merge -- now all we need is the website's cloud page to be regenerated? ikke ncopa (etc?) 2021-08-28 15:07:53 (apparently algibot only does aports) 2021-08-29 20:05:05 who can rerun alpine-mksite so we can generate an updated https://alpinelinux.org/cloud ? 2021-08-29 20:07:30 sorry, yes, I can 2021-08-29 20:08:55 thanks ikke 2021-08-29 20:23:00 tomalok: https://wwwtest.alpinelinux.org/cloud/ 2021-08-29 20:24:17 now https://www.alpinelinux.org/cloud/ as well 2021-08-29 20:24:29 I've added a make rule so that I can just do make update-cloud 2021-08-29 20:25:54 tomalok: now that the project is on github, it should even be easier to automatically update it 2021-08-29 20:25:59 gitlab*( 2021-08-29 20:55:04 ikke: (nod) thanks again 2021-08-29 23:28:44 Ariadne: was a meeting ever scheduled? 2021-08-29 23:29:47 not yet 2021-08-29 23:30:05 ok 2021-08-30 06:55:04 ikke: thank you for taking care of it 2021-08-30 07:50:46 ncopa: no problem 2021-08-31 13:27:50 I am planning tag new alpine releases today: 3.13.6, 3.12.8 and 3.11.12 2021-08-31 13:28:27 just waiting for the 3.11 builders to become idle: https://build.alpinelinux.org/ 2021-08-31 14:18:00 thanks for the heads up, ncopa 2021-08-31 20:35:31 the stable releases are tagged and uploaded and signed now 2021-08-31 20:49:42 with a bit of luck, the cloud page is automatically updated now when you push updates to the alpine-ec2-ami repo 2021-08-31 21:20:45 i'll kick off the ami builds when i get a moment to spare in between DayJob™ things 2021-08-31 21:24:02 👍 2021-08-31 23:39:46 ncopa, ikke, mcrute: https://gitlab.alpinelinux.org/alpine/cloud/alpine-ec2-ami/-/merge_requests/124 2021-08-31 23:50:13 in theory, i could merge it myself, but i'll defer to the rest o' youse if that's an okay practice for this sort of MR.