<    March 2017    >
Su Mo Tu We Th Fr Sa  
          1  2  3  4  
 5  6  7  8  9 10 11  
12 13 14 15 16 17 18  
19 20 21 22 23 24 25  
26 27 28 29 30 31
00:02 terra joined
00:10 orbiter joined
00:12 Skele joined
00:21 lesion joined
00:26 aw1 joined
00:42 blueness joined
00:45 gromero joined
00:53 gopar joined
01:39 lesion joined
02:13 slowpak joined
02:40 cyborg-one joined
02:47 s33se joined
03:03 Emperor_Earth joined
03:09 blueness joined
03:40 dirac1 joined
04:00 atomi_ joined
04:04 mguentner joined
04:09 blueness joined
04:23 blackwind_123 joined
04:26 codex joined
04:32 leprechau joined
04:38 mguentner2 joined
04:46 blueness joined
05:16 roxma joined
05:27 terra joined
06:04 terra_ joined
06:11 grayhemp joined
06:14 grayhemp joined
07:05 gopar joined
07:25 grayhemp joined
07:34 blueness joined
07:47 grayhemp joined
07:53 grayhemp joined
08:22 rrx joined
08:26 aw1 joined
08:40 fekepp joined
08:54 grayhemp joined
08:59 sergey__ joined
09:01 jackmcbarn joined
09:03 grayhemp joined
09:17 fabled joined
09:41 sparklyballs joined
09:46 slowpak joined
10:06 rollniak joined
10:16 subscope joined
10:18 orbiter joined
10:25 grayhemp joined
10:38 subscope joined
11:00 aw1 joined
11:01 aw1 joined
11:02 aw1 joined
11:03 aw1 joined
11:04 aw1 joined
11:05 aw1 joined
11:07 rrx joined
11:12 Berra joined
11:23 aw1 joined
11:25 aw1 joined
11:26 aw1 joined
11:27 aw1 joined
11:28 aw1 joined
11:30 aw1 joined
11:31 aw1 joined
11:31 transhuman_ joined
11:32 aw1 joined
11:32 atmoz joined
11:33 aw1 joined
11:34 aw1 joined
11:35 aw1 joined
11:36 aw1 joined
11:41 stwa joined
11:53 aw1 joined
11:54 aw1 joined
11:56 grayhemp joined
12:24 kunev joined
12:31 blueness_ joined
12:33 blackwind_123 joined
12:48 Urchin[emacs] joined
12:59 MDrights joined
13:23 ahrs joined
13:25 grayhemp joined
14:02 gromero joined
14:13 <transhuman_> hi! getting an error with nslookup I have never gotten before. some addresses including local machine return nslookup error nslookup: can't resolve '(null)': Name does not resolve... anyone have an idea what might be the cause
14:15 <transhuman_> whereas if I specify nslookup sample.com 8.8.8.8 it resolves or sample.com 192.168.1.1 it resolves
14:30 rollniak joined
14:31 ahrs joined
14:36 volleyper joined
14:42 Skele joined
14:45 kkyhmlmkmz joined
14:50 volleyper joined
14:56 grayhemp joined
15:32 piepy joined
15:33 <piepy> hello! While I have used Alpine with docker a bunch, I am new to installing Alpine. I am following the EC2 guide - http://wiki.alpinelinux.org/wiki/Install_Alpine_on_Amazon_EC2 - and I'm confused about "Create an amazon.apkovl.tar.gz file to put on the target" - how is this created?
15:39 <piepy> in https://gist.github.com/kennwhite/d89174749ce468f7c455 I see mention of `lbu`, but I don't see this utility in the docker image.
15:40 <piepy> is there an APK package that has `lbu`?
15:41 <fabled> piepy, it comes frmo alpine-conf
15:42 <piepy> ah yes, I just found https://github.com/alpinelinux/alpine-conf
15:42 <fabled> alpine-base depends on it, so you normally should get it
15:42 <fabled> if you are doing minimal setup using your own top level deps without alpine-base, then it might be missing
15:42 <fabled> normally we assume 'alpine-base' is installed
15:42 <piepy> but I guess it doesn't really make sense to put it in the alpine docker image
15:42 <fabled> not really
15:43 <piepy> is `lbu` the best way to create the apkovl?
15:43 <fabled> that's the current standard way to do it from running system
15:43 <fabled> the image builder creates it manually, though
15:43 <piepy> the ISO image builder?
15:43 <fabled> lbu uses apk to construct the list of files to store
15:43 <fabled> yes, the iso image builder
15:44 <piepy> OK, I can probably look up the scripts used in that builder. I will give `lbu` a shot first
15:44 <fabled> apkovl is currently just a .tar.gz containing the changed files
15:45 <piepy> I don't see an existing EC2 image for alpine, so I am working on using packer to auto-build one
15:45 <fabled> previously I built only private images. there's been discussion on providing public EC2 images, but not sure where that is currently
15:46 <piepy> yea, that's understandable
15:46 <piepy> if I'm successful, I'll share my work and see if it's helpful to the project
15:46 <piepy> thanks for the info, I'll see if I can create the apkovl from here
15:46 <TemptorSent> What exactly would be needed for the image?
15:48 <piepy> TemptorSent: http://wiki.alpinelinux.org/wiki/Install_Alpine_on_Amazon_EC2 ?
15:49 <piepy> there are a few details EC2 wants to see (SSH/networking, mostly, I think)
15:51 <TemptorSent> piepy: Do you happen to know more about what's needed in terms of kernel/modules? I've already taught my branch of mkimage to autogenerate SSH keys for images.
15:51 <piepy> I don't, I'm feeling my way around the dark here
15:52 <piepy> I'm not sure how it will go, though I hope to have a minimal image as a container base that boots fast and is more enjoyable to use than coreos
15:52 <TemptorSent> piepy: Okay, I have the virt-profile pared down to almost nothign and happy under qemu, but EC2 is on Xen, right?
15:53 <TemptorSent> piepy: Can you pop into a coreos image and get the list of required modules perhaps?
15:54 <TemptorSent> (Running requirements)
15:55 Berra joined
15:58 <TemptorSent> piepy: You can take a look at https://github.com/TemptorSent/aports/tree/mkimage-refactor-scripts/scripts/mkimage and give it a try if you like. Minimal invocation is ./mkimage --repository-file /etc/apk/repositories --profile virt' You also probably want to set --workdir and --outdir to somewhere.
15:59 <piepy> TemptorSent: yes, EC2 is Xen. I am starting with the Xen ISO image
15:59 <piepy> TemptorSent: what does mkimage do? build an ISO?
15:59 <TemptorSent> piepy: virt currently has just the virtio drivers an not much else, so you may need to add the initfs feature virt-guest-compat.
16:00 <piepy> I ought to be able to load up a CoreOS image and check the modules in a bit, sure. I first want to get my apkovl file integrated and run packer at least once.
16:00 <TemptorSent> piepy: Yes, it builds iso (and tarballs, or whatever you want really)
16:00 <piepy> cool
16:01 <TemptorSent> piepy: It looks like the wiki page is a full major version and then some out of date, so you may find things don't quite line up.
16:01 <TemptorSent> piepy: It also has features that you can use to autogenerate ssh keypairs, autostart dhcp, postgres, etc.
16:02 <TemptorSent> piepy: So no lbu step should be neede -- you can write one-off profiles in your ~/.mkimage directory for your exact configuration, including writing what you want added to the overlay.
16:03 <TemptorSent> piepy: I'm working on cleaning up the overlay system somewhat, as well a rewrite of the initramfs init system.
16:05 <piepy> ATM I just want to see a Alpine boot on EC2 :)
16:05 <piepy> I'll get deeper into this once I have that working
16:12 <TemptorSent> piepy: Given the right modules, you should be able to just drop the image in an run.
16:12 <piepy> I'm not sure what you mean by "drop the image in and run"
16:13 <TemptorSent> piepy: You shouldn't need to do any of the setup steps other than getting it to boot.
16:13 <TemptorSent> setting dhcp, sshd, keys, etc.
16:14 <piepy> I don't want to have to build an ISO to then build the EC2 AMI. I want to "run one thing" that ends up with an AMI.
16:14 <piepy> building an ISO means hosting it too
16:15 <piepy> If there was an ISO for EC2, I'd use that, but then alpine might as well build an AMI as well
16:15 <TemptorSent> piepy: Right, that's why I'd like to add direct output for AMI :)
16:15 <TemptorSent> piepy: I just need to know what it requires.
16:15 <piepy> I'll hang around here a bit and let you know how my experiment goes :)
16:16 <TemptorSent> piepy: It should just be a matter of adding the proper definition for the imagetype and whatever it needs to package it properly.
16:18 grayhemp joined
16:19 <TemptorSent> piepy: It looks like Amazon makes it hard to build an EBS image without being on thier service.
16:21 <TemptorSent> piepy: I wonder if the instance store is more sane...
16:22 <piepy> yea, you would need an account to create an AMI (you have to run an instance, create the AMI from the instance, and then that AMI is stored on S3, which costs $)
16:23 <piepy> you can probably build the AMI on the free tier, but storage on S3 is $
16:23 <TemptorSent> piepy: Yeah, trying to figure out what would be needed to just drop into an AMI and bundle at least.
16:24 <piepy> "drop into an AMI" == "run an instance using an AMI"
16:24 <piepy> does alpine use /etc/network/interfaces?
16:25 <TemptorSent> Yes, it does.
16:26 <piepy> ah yes, found the helpful page in the wiki
16:27 <TemptorSent> piepy: Can you downlad your image from AWS and inspect it?
16:27 orbiter joined
16:28 <piepy> um.. not really. You could build an OVA and _import_ it into AWS, but I guess that wouldn't really help you
16:28 <TemptorSent> piepy: I'm trying to figure out how to dump in at least the full FS image so you could start an instance and import with a couple commands.
16:29 <TemptorSent> Can you mount a file as a device?
16:30 rrx joined
16:32 lesion joined
16:32 wonton joined
16:33 <piepy> TemptorSent: mount a file as a device? like an ISO as a loopback? yes
16:34 <TemptorSent> piepy: ISO would work I suppose, but something like a squashfs would be nice :)
16:35 <TemptorSent> piepy: Something that can be used to bootstrap the build process anyway.
16:35 <piepy> I'm not sure what isn't clear.. EC2 is Xen, you can run Linux/BSD/etc on it - if you run linux, it's just like linux elsewhere
16:35 <piepy> I'm bootstrapping my build on ubuntu
16:35 <TemptorSent> piepy: Right, I mean what you can mount to amazon as a EBS
16:36 <TemptorSent> piepy: I'm seeing ephemeral an EBS.
16:36 <piepy> EBS is just a way to create/attach a volume, just like a HD
16:37 <TemptorSent> piepy: Exactly, if you could import such a volume directly, all that would be missing is the aws bundling I believe.
16:38 <TemptorSent> piepy: I'm looking at EFS right now, which might be an option.
16:38 <piepy> EFS == NFS, I don't see how that would help
16:39 <TemptorSent> piepy: NFS root :)
16:39 <TemptorSent> piepy: Then an iso can be used to bootstrap and all config be stored on the EFS.
16:42 <piepy> why would that be necessary?
16:43 <TemptorSent> piepy: So we could generate a single iso image to then create any number of configured instances once it's bootstrapped.
16:45 <TemptorSent> Ahh, it looks like the old ec2-ami-tools will allow importing!
16:49 <TemptorSent> Or you can register an image stored in s3 storage somehow, although it's not entirely clear on WHAT kinf of image.
16:50 <TemptorSent> Does it want a raw block device? A device partitioned using BIOS disk lables? EFI?
16:51 <TemptorSent> Basically, what does their environment need for an image to be BOOTABLE?
16:54 ahrs joined
16:57 <TemptorSent> piepy: Basically, with enough information about what the image format and boot parameters, I should be able to spit out either a complete image or a tarball ready to be extracted to a EBS device inside a running instance that could then be turnd into it's own EBS image.
17:06 <piepy> TemptorSent: yes, if you build an ISO that's fit for AWS, that's better than the current process
17:29 cyborg-one joined
17:31 <TemptorSent> piepy: That's what I'm shooting for.
17:39 dirac1 joined
17:43 fabled joined
17:44 <piepy> is `lbu` aware of packages? eg, could I say "ensure you backup all pkg that were installed", or do I need to explicitly add/include each file for each package?
17:48 wonton_ joined
17:48 <fabled> piepy, yes, it stores etc/apk/world, and apk restore the packages on tmpfs boot; apk cache needs to be enabled for that
17:55 <piepy> ah, ok.. so if I install a package with `apk add foo`, the foo package would be restored, but if I use `apk add --no-cache foo`, I don't get that.
17:55 Nobabs27 joined
17:56 <TemptorSent> fabled: Would you see any problem with sending ALL init output to /dev/kmsg and eliminating the rest of the mess with quiet?
17:57 <TemptorSent> fabled: Then just toggling dmesg with the quiet flag (or setting it to ERR) and running dmesg on error when we start a recovery shell?
17:58 volleyper left
18:10 <TemptorSent> fabled: Implemented with a wrapper like "run() { $@ > /dev/kmod 2>&1 || handle_error ; }
18:12 <TemptorSent> fabled: Hmm, I may have lied, log may need to be a function because kmsg (oops, not kmod!) wants '<N> msg'
18:12 bozonius joined
18:24 wonton joined
18:30 grayhemp joined
18:38 BitL0G1c joined
18:39 grayhemp joined
18:39 vectr0n|cloud joined
18:43 grayhemp joined
18:48 dirac1 joined
18:51 subscope joined
18:53 <TemptorSent> fabled: Solved -- twiddle the /proc/sys/kernel/printk values instead :)
19:11 grayhemp joined
19:14 stwa joined
19:19 atmoz joined
19:19 grayhemp joined
19:39 vectr0n joined
19:40 npx joined
19:42 <npx> Hey guys, I have a vagrant box - atlas.hashicorp.com/hypoalex/boxes/alpine - that I built using https://github.com/hypoalex/packer-templates/tree/master/alpine and it's failing to mount the vboxsf filesystem, the mount command doesn't return any errors. Any idea what I'm missing here?
19:42 lnds joined
19:44 <npx> https://github.com/hypoalex/packer-templates/blob/master/alpine/scripts/05virtualbox.sh#L6-#L10 - It's loading and detecting the guest additions when I do a `vagrant up`
19:56 <transhuman_> hi! getting an error with nslookup I have never gotten before. some addresses including local machine return nslookup error nslookup: can't resolve '(null)': Name
19:56 slowpak joined
19:56 <transhuman_> does not resolve... anyone have an idea what might be the cause
19:56 <transhuman_> whereas if I specify nslookup sample.com 8.8.8.8 it resolves or sample.com 192.168.1.1 it resolves
20:01 <atmoz> How does Alpine stack up against container distros like CoreOS? I'm considering slim distros to run Kubernetes. Anyone have experience with Kubernetes and Alpine?
20:06 <_ikke_> alpine is not specifically a container OS, it's just very small
20:07 blueness joined
20:08 <piepy> atmoz: I haven't yet run kube ON alpine (though I'm working towards getting there), but I have run coreos a bunch (as a host on EC2), as well as alpine as a docker container. I would like to run alpine on EC2 to run kube/nomad on it, primarily b/c I want a minimal base OS that is also easy to admin and work with. I'm tired of Ubuntu, and I'm super annoyed by coreos making admin difficult (no package manager, forces you to build
20:08 grayhemp joined
20:10 <Xe> piepy: i'd be interested in collaborating for kube on alpine, do you have package build files defined yet?
20:11 <piepy> I'm currently working on automating a build for the EC2 image - haven't gotten to the part where I "run Alpine on AWS"
20:11 <TemptorSent> piepy: Is it possible to download your image from the s3 storage?
20:12 <TemptorSent> piepy: A little forensics and we should be able to spit one out.
20:12 <piepy> I haven't yet gotten packer to build, still futzing with it (but almost there)
20:12 <TemptorSent> gotcha
20:12 <TemptorSent> I'm still trying to figure out what the initfs-init really needs and doesn't, as well as giving real logging.
20:22 parazyd joined
20:22 parazyd joined
20:31 asie joined
20:59 <transhuman_> anyone know what package provides nslookup is it net-tools or something
21:00 gopar joined
21:06 blueness joined
21:14 <piepy> TemptorSent: I am able to build and run an AMI, but I haven't yet gotten it to stay running - there are some AWS requirements I must be missing (AWS wants to be able to write SSH key and some other stuff)
21:16 czart__ joined
21:26 wonton joined
21:46 blueness joined
21:48 gopar joined
21:51 blueness joined
22:02 blueness joined
22:03 wonton_ joined
22:10 <kahiru> transhuman_: bind-tools
22:18 czart joined
22:20 <TemptorSent> piepy: Hmm, how does it go about writing the ssh keys?
22:24 <transhuman_> thanks kahiru
22:41 MDrights joined
22:44 dirac1 joined
22:56 grayhemp joined
22:58 minimalism joined
22:58 lesion joined
23:00 stwa joined
23:22 <piepy> TemptorSent: IDK, need to do some more research, I'll dig in some more and report back when I have results
23:25 linus_ joined
23:28 <TemptorSent> piepy: Sounds good.
23:58 orbiter joined