<     May 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:00 silviof joined
00:07 grayhemp joined
00:20 sparklyballs joined
00:39 dka_ joined
00:39 <dka_> Hi everyone!
00:39 <dka_> I have the following error during a build in Alpine Linux : "error while loading shared libraries: libpng12.so.0:"
00:40 <dka_> Do you know what dependency I am missing ? I have tried to install libpng and gd but it didn't change
00:40 <scv> that's the bit before the error, not the actual error
00:41 <dka_> ERROR in ./app/static/StarterTemplateExample.png
00:41 <dka_> Module build failed: Error: /mnt/mesos/sandbox/builds/docs/bootstrap-styled/node_modules/pngquant-bin/vendor/pngquant: error while loading shared libraries: libpng12.so.0: cannot open shared object file: No such file or directory
00:44 <scv> well, the version of libpng shipped in alpine is 1.6 - i.e. libpng16
00:44 <scv> if your code absolutely requires 1.2 you may need to build it yourself
00:45 <dka_> scv, I have tried to install libpng16 but it wasn't found
00:45 <dka_> instead I have installed libpng
00:45 <scv> that is libpng16
00:45 <dka_> can I have both ?
00:45 <scv> there is no libpng12 package
00:45 <scv> if your code absolutely requires that version you'll need to build it yourself
00:47 <Bun> seems like the pngquant-bin npm hasn't updated its stuff in a couple of years: https://github.com/imagemin/pngquant-bin/tree/master/vendor/linux
00:54 <Shiz> dka_: you should probably definitely not use precompiled packages
00:54 <Shiz> there is a very high chance that it will not work on alpine
00:54 <Shiz> third-party precompiled packages that is, like that pngquant
00:55 <dka_> well. it is one of the sub sub sub library of one of my npm dependency
00:55 <dka_> I think it is the npm package "image-webpack-loader"
00:55 <dka_> I have updated from v2 to v3 and I am trying again
00:56 <dka_> Shiz if there is an high chance that it does not work in alpine
00:56 <dka_> the problem I have is that I am working within a docker container. And for some reason, it must be a Dockerfile created using `FROM docker:latest`
00:56 <dka_> I have checked all the docker Dockerfile and they are all using alpine
00:57 <dka_> so I guess I am a bit stuck with alpine. So is it possible to do that build in any way ?
00:57 <Shiz> what you could do, and mind you i have no idea if this works
00:57 <Shiz> because i don't know how npm works
00:57 <Shiz> is install alpine pngquant and remove the offending precompiled binary
00:57 <Shiz> and symlink it to alpine pngquant
00:58 <Shiz> # apk add pngquant and then ln -sf /usr/bin/pngquant /mnt/mesos/sandbox/builds/docs/bootstrap-styled/node_modules/pngquant-bin/vendor/pngquant
00:58 <Shiz> I don't have enough knowledge of npm to tell you if this is possible between installing the package and it trying to invoke it, though
00:58 mrEngineer joined
00:59 <dka_> Yes
00:59 <dka_> it will work
00:59 <dka_> I guess
00:59 <dka_> but that's ugly
00:59 <Shiz> not as ugly as people shipping precompiled binaries :)
01:00 <Shiz> horrible practice on Linux machines imo, especially dynamically linked as that one seems to be
01:00 <Shiz> but personal opinions and all that
01:00 <Shiz> a more cleaner solution, I presume, would involve making your own fake pngquant-bin package and have npm pick up on it
01:00 <Shiz> that ships no binaries and its entry point just points at the system pngquant
01:01 <Shiz> but again, not enough knowledge of npm here to tell you how to exactly do that
01:01 <dka_> it will work
01:01 <dka_> I guess, I don't see why. But this will fix this error for I guess another one
01:02 <dka_> I was having the dependency from this bundle: https://github.com/tcoopman/image-webpack-loader/blob/v2.0.0/package.json
01:02 <Shiz> because precompiled binaries are not guaranteed to work across all Linux machines, as you just saw
01:02 <Shiz> especially dynamically linked ones
01:02 <dka_> I am trying to replace it for that one https://github.com/tcoopman/image-webpack-loader/blob/v3.3.1/package.json though I am not even sure if it will change anything
01:02 <Shiz> only the ones the author happens to have on hand, which is usually ubuntu and with some luck centos :P
01:03 <Shiz> i don't think it will
01:03 <scv> its possible to build semi-universal bins but nobody ever seems to bother
01:03 <scv> mainly because anybody who understands how also understands why its a bad idea :p
01:03 <Shiz> yeah, you can do it with statically-linked musl binaries :P
01:05 <Bun> that module pulls in a bunch of other packages that has similarly old (and even older) binaries, so probably not going to help you
01:05 <scv> ah, the wonderful world of nodejs packages
01:06 <scv> just stuff it into some opaque package, nobody's ever gonna need to touch it (/s)
01:06 <Bun> that's why you put it in a container, so you never have to update it :^)
01:11 <dka_> ok
01:11 <dka_> So I guess
01:11 <dka_> my best option is not to use alpine for the build
01:12 <dka_> may I ask how can I have a docker without alpine (debian)
01:12 <Bun> you change the FROM part to something else
01:12 <dka_> it needs to be docker
01:12 <dka_> otherwise it doesn't work
01:12 <scv> that's a docker question rather than an alpine question
01:13 <Bun> the FROM thing selects the base "OS", so that's what you need to change
01:13 <dka_> If you look at all the example of docker in docker (dind), you will notice that they use "docker" as image. This is the only image that work with dind. What I did is to extend this image and installed nodejs, jdk, etc... myself
01:14 <Bun> if you have docker in docker, why not put your debian container in the docker in the docker
01:14 <scv> infinitely docked
01:15 <dka_> because when I install docker inside debian, I have this error "Cannot connect to the Docker daemon. Is the docker daemon running on this host?"
01:16 <dka_> this error doesn't happen when I use docker image
01:16 <Bun> no no, you have docker running on alpine, and on that docker instance you install your debian container
01:16 <dka_> it's not how gitlab-ci work
01:16 <dka_> :D
01:17 <Bun> sounds terrible
01:17 <dka_> I know. But I must say thanks a lot for trying so hard
01:18 <scv> boy that sounds rough
01:18 <dka_> Yes you are right image-webpack-loader@3.3.1 doesn't change anything, same error.
01:19 <dka_> So I need to reproduce docker:latest on a base image debian
01:19 <dka_> This is the Dockerfile: https://github.com/docker-library/docker/blob/5a196cae40e2a0ab5050cf6d79b697e032352b24/17.05/Dockerfile
01:19 <dka_> any idea how I could start ?
01:20 <scv> lol
01:20 <dka_> Oh I think I got it
01:20 <Bun> s/apk add/apt install/ probably
01:21 <scv> stuff like this makes me regret being interested in computers, i should just go run a taco truck and not subject myself to this madness :D
01:22 <Bun> sounds good, can I visit
01:22 <scv> sure
01:30 s33se joined
01:30 grayhemp_ joined
01:30 tmh1999_watcher joined
01:44 czart joined
01:55 grayhemp joined
02:18 ogres joined
02:23 greguu joined
02:32 tmh1999_watcher joined
02:42 <mepholic> honk hole
02:50 grayhemp joined
03:21 Classsic_ joined
03:22 <Classsic_> hi, somebody know how create custom iso?
03:44 orbiter joined
03:51 grayhemp joined
04:16 ogny joined
04:35 czart joined
05:17 s33se_ joined
05:57 ogny joined
06:55 eqc_ joined
06:55 serge____ joined
07:03 fabled joined
07:55 orbiter joined
08:19 grayhemp joined
08:32 thestranjer joined
08:32 <thestranjer> Hey
08:32 <thestranjer> Is anybody on?
08:33 Marc1n joined
08:34 <Bun> guess not
08:36 <thestranjer> Kek
08:36 <thestranjer> Are you an Alpine "expert" by any chance, Bun?
08:37 <Bun> alpine certified engineer, yes; how can I help you today?
08:40 <thestranjer> Alright, well, I'm new, so sorry if this question is super duper obvious.
08:40 <thestranjer> I have an HP Stream 13, and the NIC on that does not play nice with Linux. It's a BCM43142
08:40 <thestranjer> Now, I can get it running on Ubuntu by install a couple of packages with dpkg
08:40 <thestranjer> However, I'm not sure if that's appropriate -- or would even work -- using Alpine.
08:41 <thestranjer> Also I'm aware that you may have been joking about being an Alpine certified engineer but I don't care.
08:41 <thestranjer> Even if you were you might know what the deal is.
08:41 <Bun> well, that depends on what is in those debs or whathaveyou
08:42 <Bun> just the kernel module? and/or firmware?
08:43 <Bun> this seems relevant: https://pkgs.alpinelinux.org/package/v3.6/main/x86/b43-fwcutter
08:43 <thestranjer> Well, one of them was dkms, and the other one is bcmwl-kernel-source
08:44 <thestranjer> That seems extremely relevant actually
08:46 <Bun> https://wiki.alpinelinux.org/wiki/Connecting_to_a_wireless_access_point also some special instructions here in the bottom section
08:46 ogny joined
08:46 <thestranjer> Oh wow, this is great, man.
08:51 <thestranjer> Thanks a lot
08:53 ^ingo^^^ joined
08:58 ^ingo^^^^^ joined
09:02 ^ingo^^^ joined
09:05 Mr_H joined
09:06 aw1 joined
09:06 arnotixe joined
09:31 ncl joined
10:45 minimalism joined
10:46 cyborg-one joined
10:58 helpImStuck joined
11:23 cja_ joined
11:25 cyteen joined
11:26 emacsoma` joined
11:39 blackwind_123 joined
11:50 blackwind_123 joined
12:07 bOSKE joined
12:12 tmh1999 joined
12:29 shinx joined
12:29 dka__ joined
12:37 LouisA joined
12:38 gromero joined
12:48 ogres joined
12:51 eqc_ joined
13:04 grayhemp joined
13:16 dka_ joined
13:22 dka_ joined
13:22 psychi[Arch joined
13:32 czart_ joined
13:33 fcolista joined
13:42 <Tsutsukakushi> https://ollieparanoid.github.io/post/postmarketOS/ <= you guys seen this?
13:42 <Tsutsukakushi> (alpine based)
13:43 <scadu> posted on another Alpine channel
13:43 fcolista joined
13:59 tmh1999 joined
14:03 Skele joined
14:18 orbiter joined
15:01 baliste joined
15:31 dka__ joined
15:42 emacsomancer joined
15:43 dka_ joined
15:50 dka__ joined
15:52 <Shiz> Tsutsukakushi: neat
15:56 ogny joined
16:54 ogny joined
17:00 ogres joined
17:41 eqc_ joined
17:46 cyborg-one joined
17:52 grayhemp joined
18:03 grayhemp joined
18:04 emacsoma` joined
18:13 malucious joined
18:17 cyadoux joined
18:20 grayhemp joined
18:22 thestranjer joined
18:35 eqc_ joined
18:55 f joined
18:57 <Guest58142> Hi! Any of your are using Alpine as your main OS? I mean, in your laptop or desktop PC, and not inside a VirtualMachine.
18:58 <Guest58142> (I'm considering install Alpine as my main OS, but I want to know your experiences first, thanks)
18:58 <Guest58142> (I'm currently using ArchLinux, used Debian, Ubuntu in the past)
18:59 malucious left
19:21 <Shiz> Guest58142: I ran it on my desktop for a while before I ditched my desktop
19:21 <Shiz> I am currently running it on all of my servers
19:21 <Shiz> and I know at least two people who use it as laptop OS
19:21 <Shiz> :P
19:26 <Guest58142> Shiz: tks!
19:28 blackwind_123 joined
19:49 fweinb joined
19:49 ahrs joined
19:51 <fweinb> Hi there. Just trying to get Alpine Linux to boot on the new Udoo X86 board (https://www.udoo.org/docs-x86/Introduction/Introduction.html) setup-alpine works great but after rebooting it can't find the boot device. I tried to install it to the internal emmc (/dev/mmcblk0). It looks like that the initramfs can't access emmc devices. Any hints?
19:54 <Shiz> hmm, sounds like you may need to add the relevant modules to mkinitfs.conf
19:58 <fweinb> I just used the alpine standard iso from the website. So I need to build the initramfs myself?
19:59 <Shiz> the initramfs is always built locally when you do an install
19:59 <Shiz> :)
19:59 <Shiz> mkinitfs.conf just tells it which kernel modules etc it should contain
20:01 fcolista joined
20:06 <fweinb> Sorry but I am new to this and can't find the mkinitfs.conf when I boot from the usb stick i created
20:07 <Shiz> it should be present after you run setup-alpine, on your target disk
20:08 <fweinb> But I can't boot into the target disk? Can I modify it after the installation from the usb boot?
20:08 <Shiz> yeah
20:12 <fweinb> I mounted mmcblk0p3 to /mnt/system/ and can now access /etc/mkinitfs/mkinitfs.conf now I do need to find the emmc driver and add it into the features string, right?
20:14 <Shiz> right, if you chrooted into that rootfs, you should find the kernel module that applies to your mmc device and add it to /etc/mkinitfs/mmc.modules
20:14 <Shiz> and make sure mmc is in the features string in mkinitfs.conf
20:14 <Shiz> lspci -k can help you with figuring out the module name
20:15 <Shiz> sorry, /etc/mkinitfs/features.d/mmc.modules
20:17 <fweinb> Okay. added the string "mmc" to the feature list. Now I need to find which module I need for mmc support. lspci -k just lists some classes and names hard to guess which one is the right one. I have no idea how to chroot the rootfs
20:17 Nobabs27 joined
20:19 <Shiz> oh, mmc wasn't already in there?
20:19 <fweinb> lspci -k is kinda cryptic. Nothing named mmc
20:20 minimalism joined
20:20 <Shiz> in the feature list, I mean
20:20 <Shiz> if it wasn't already in the feature list, that may be enough to make it work :p
20:20 <Shiz> do you have a separate boot partition?
20:21 <fweinb> Yeah boot is on mmcblk0p1
20:22 <Shiz> and root on p2?
20:22 <fweinb> p3 i guess, that is what I mounted to edit the mkinitfs.conf
20:22 <Shiz> right
20:22 <Shiz> then p2 is probably swap
20:23 <Shiz> what you want to do is
20:23 <Shiz> chroot into the installed system, as such:
20:23 <Shiz> mount /dev/mmcblk0p1 /mnt/system/boot
20:23 <Shiz> mount --rbind /dev /mnt/system/dev
20:23 <Shiz> mount -t proc none /mnt/system/proc
20:23 <Shiz> mount -t sysfs none /mnt/system/sys
20:23 <Shiz> chroot /mnt/system
20:24 <Shiz> you should now be 'inside' the installed system with everything properly mounted
20:24 <Shiz> can you btw answer my above question if mmc was already in the feature list or not? :p
20:24 <fweinb> No it was not.
20:24 <Shiz> ah, okay
20:25 <Shiz> that's weird, I thought it was by default
20:25 <Shiz> what does your /etc/mkinitfs/mkinitfs.conf look like now?
20:27 <fweinb> sorry give me a sec to chroot.
20:29 <Shiz> np
20:32 <fweinb> featrues="ata base ide scsi usb virtio ext4 mmc" (mmc was added by me)
20:32 minimalism joined
20:33 denaltroy joined
20:39 <fweinb> So I assume I just no run "mkinitfs -c /etc/mkinitfs/mkinitfs.conf -b /" to recreate the initfs?
20:44 <Shiz> fweinb: just # mkinitfs should be enough
20:44 <Shiz> also i hope you spelt features right in the actual file ;)
20:44 <fweinb> Oh yes just a typo here.
20:44 LouisA joined
20:45 <fweinb> I will try rebooting. Thanks for your help.
20:46 <fweinb> Awesome! Its running!
20:48 <fweinb> But maybe mmc should be included by default.
20:52 minimalism joined
20:53 <Shiz> yes, I think it was before...
20:54 <Shiz> Sorry you had to deal with that :P
20:57 <fweinb> No problem. Amazing support! Thank you.
20:58 <Shiz> \o
21:18 eqc_ joined
21:21 hmrodrigues joined
21:22 <hmrodrigues> hey guys, I'm trying to run alpine on kvm but it doesn't detect the network interface
21:23 <hmrodrigues> I use libvirt.
21:23 <Shiz> what NIC type are you using?
21:23 <hmrodrigues> the cmd I used to create the vm: virt-install --connect qemu:///system --name alpine --memory 2048 --vcpus 1 --cpu host --cdrom /var/lib/libvirt/iso/alpine-virt-3.6.0-x86_64.iso --disk size=10 --network network=default --graphics spice --video qxl --channel spicevm
21:27 <scv> so what sort of emulated NIC are you using?
21:30 <scv> alternatively have you configured the network in libvirt?
21:36 <hmrodrigues> How can I see the type? I just use the default network
21:36 <hmrodrigues> network works on other virtual machines out of the box
21:41 <BitL0G1c> hmrodrigues - inside alpiine you need to run /sbin/setup-interfaces
21:42 <BitL0G1c> & probably - rc-update add networking
21:43 lesion joined
21:44 <hmrodrigues> @BiL0GIc ip a still only shows lo
21:44 <hmrodrigues> if I add eth0 to /etc/networking/interfaces it says that it can't find the device
21:46 <Shiz> hmrodrigues: uuh
21:47 <Shiz> hmrodrigues: dump the libvirt xml, it should be in a <model> field within <devices> -> <interfaces>
21:49 <hmrodrigues> rtl8139'
21:49 <Shiz> ah
21:49 <darkfader> wtf
21:49 <darkfader> ah, emulated
21:49 <darkfader> i was in shock for a moment
21:50 <Shiz> lol
21:50 <Shiz> hmrodrigues: one sec
21:51 <hmrodrigues> @Shiz alright
21:51 <Shiz> okay, what happens if you # modprobe 8139cp
21:52 <hmrodrigues> not found in modules.dep
21:52 <Bun> the virt kernel only has virtio iirc
21:53 <Shiz> ah
21:53 <Shiz> hmrodrigues: are you using the virt kernel?
21:55 <hmrodrigues> yes
21:56 <hmrodrigues> working now, I told libvirt to use virtio
22:00 <hmrodrigues> as I'm already here, when should I run alpine from the disk and when it should run from tmpfs in virtual machines?
22:02 <hmrodrigues> is tmpfs only for data storage or it can be used to deploy an app or host postgres?
22:03 <Bun> the name tmpfs gives it away doesn't it? if you want persistance, store things on disk
22:04 <Bun> and running postgres purely from memory/swap may or may not work depending on how much memory you have available
22:05 <hmrodrigues> when I say tmps I'm saying run alpine from tmpfs. like when running setup-disk the step where is asks how to use the drive
22:05 <hmrodrigues> postgres was an example haha
22:05 <kaniini> if you are running postgresql, you most likely do not want to run from tmpfs
22:06 <kaniini> tmpfs is mostly for setups where configuration is separate from data
22:06 <kaniini> such as hypervisor control planes
22:06 <kaniini> in such case, you would run from tmpfs and store your disk images on your disks (provisioning them however you wish, likely with lvm(8))
22:07 <kaniini> that way if there is a disk problem you can log in and diagnose the issue
22:07 <hmrodrigues> oh ok I understand
22:16 mdillon joined
22:17 emacsoma` joined
22:26 gattuso joined
22:31 cyadoux left
22:56 robru joined
22:57 Tritlo joined
22:58 krainboltgreene joined
23:01 Death_Syn joined
23:01 zoidbergwill joined
23:01 zopsi joined
23:17 emacsoma` joined
23:29 atomi joined