News for hackers. Stuff that matters.
Re:In Praise of Alpine and APK by PhilipRoman on Monday February 20, 2023 @03:59PM (#34872825)
I agree with the author about /etc/APK/world.

APK has become my favorite package manager - so far I've had zero breakage with it, unlike apt and pacman which have lots of sharp corners. The same can be said about Alpine Linux in general.

For the last 6 months I have been experimenting with running a zero-maintenance weekly upgrade+reboot cronjob on my Alpine server. Obviously a bad idea but I just want to see how long it takes for something to break.

Re:In Praise of Alpine and APK by nrclark on Monday February 20, 2023 @04:41PM (#34873328)
Alpine is great, and I have nothing bad to say about it. I'm curious though: what sharp corners have you found with apt? I've been a Debian user for 20 years and I've never had any problems relating to apt/dpkg.
Re:In Praise of Alpine and APK by hawski on Monday February 20, 2023 @05:33PM (#34873848)
For me personally apt is just annoyingly slow, but dnf is much worse. I've seen how fast APK is and I feel, that my distro of choice (Void) has a package manager (XBPS) that is maybe slightly slower than it.

I sometimes wonder if it is like that, because XBPS and APK were designed and built by C hackers while apt where done by system administrators maybe. With dnf/rpm I attribute it to this quirkiness I often feel diving into some of Red Hat's tech. Not trying to offend, just wondering and I acknowledge that I am biased.

Re:In Praise of Alpine and APK by invalidator on Monday February 20, 2023 @06:22PM (#34874248)
> apt is just annoyingly slow

A lot of that is due to aggressive use of fsync. apt tries hard to be robust against power failures when changing the system.

When using it for something ephemeral (say, part of a CI workflow) you can disable fsync and let it rip. It's still not as fast as apk but it's several times faster than normal.

  apt-get -yq install eatmydata
  eatmydata apt-get -yq install (all the other things)
Re:In Praise of Alpine and APK by gorgoiler on Monday February 20, 2023 @11:25PM (#34876574)
Wow. You weren’t kidding.

I tried apt install ffmpeg in a debian:sid docker container on two different docker hosts: one with slow IO (a cheap VPS with slow, contentious storage); and one with much faster, less over subscribed IO.

Fast IO: 27s -> 26s with eatmydata. Basically the same.

Slow IO: 280s -> 140s with eatmydata. Literally twice as fast.

Re:In Praise of Alpine and APK by PhilipRoman on Monday February 20, 2023 @05:08PM (#34873612)
Never used pure Debian so I don't know how much of this is Ubuntu's fault but just today I had to fix a similar issue as described here: https://askubuntu.com/questions/1097066 Also the solution somehow ended up uninstalling the desktop environment. Still scratching my head over that one. It wasn't my own system though.
Re:In Praise of Alpine and APK by pxc on Monday February 20, 2023 @06:39PM (#34874399)
* * *
Re:In Praise of Alpine and APK by PhilipRoman on Tuesday February 21, 2023 @01:10AM (#34877337)
Thanks, this was an interesting writeup. Learned a few new things today.
Re:In Praise of Alpine and APK by pxc on Monday February 20, 2023 @04:27PM (#34873159)
> /etc/APK/world

[FTA:]

> I was very pleased to learn about apk’s /etc/apk/world.

> In essence, this file is a list of desired packages, and apk will install and uninstall packages so that the system state converges to the list. Exactly what I’d been looking for, but built right into the package manager. Actually it’s not just built into the package manager: it’s the very foundation of how it works. apk add actually adds a package to that list, and then installs any that are not present. apk del removes a package from that list, and only uninstalls it if it’s not a dependency for anything else.

This is fairly standard for how package managers work, afaik. From memory, Debian-based systems (in /var/lib/dpkg/status, IIRC) and Gentoo systems both work that way: constraints for the dependency solver (desired versions) are written to a persistent file in a plaintext format before the depsolver runs. In Gentoo's case, the language is also the same— the file is 'the world file' and it lives at /var/lib/portage/world.

I don't have an Arch system in front of me but I imagine it also stores its package selection database in a (perhaps compressed) plaintext format like this.

The novelty here is actually in encouraging users to edit the file directly by directing attention to it in the docs and by storing it under /etc, where one expects admin-facing configuration files.

Definitely an improvement over the norm on Linux, imo.

> apt and pacman which have lots of sharp corners

I'd love to hear more about these!

Re:In Praise of Alpine and APK by mid-kid on Monday February 20, 2023 @06:58PM (#34874578)
I'm not sure arch stores it in an explicit file, but pacman -Qe lists all explicitly installed packages, and anything not required will be listed in pacman -Qdt

Now, it is nice that "apk del" and such automatically takes care of removing unused packages, such that you never need an "autoremove" step or similar.

Re:In Praise of Alpine and APK by signa11 on Tuesday February 21, 2023 @01:24AM (#34877435)
>> In essence, this file is a list of desired packages, and apk will install and uninstall packages so that the system state converges to the list. Exactly what I’d been looking for, but built right into the package manager. Actually it’s not just built into the package manager: it’s the very foundation of how it works. apk add actually adds a package to that list, and then installs any that are not present. apk del removes a package from that list, and only uninstalls it if it’s not a dependency for anything else.

> This is fairly standard for how package managers work, afaik.

i don't think there is a similar concept as that of `/etc/apk/world` in archlinux. from the article it seems that it is a list of packages that i want, and then you let `apk` run its course, installing everything (and its dependencies) mentioned therein.

not sure about debian, but for gentoo `/var/lib/portage/world` see this: https://wiki.gentoo.org/wiki/Selected-packages_set_(Portage)... regarding editing that file by hand. it will be overwritten (and _aggresively_ at that)

Re:In Praise of Alpine and APK by jraph on Tuesday February 21, 2023 @02:11AM (#34877765)
In the Debian world, that would be the dpkg selections I think. You can mark a package as installed manually or automatically, and if it's installed automatically it can be auto removed later.
Re:In Praise of Alpine and APK by yjftsjthsd-h on Monday February 20, 2023 @04:10PM (#34872954)
> Obviously a bad idea but I just want to see how long it takes for something to break.

That's not quite so obvious to me. First, I don't immediately recall ever having any problems resulting from upgrading within a release (i.e. if I'm on 3.16, I don't remember `apk upgrade` ever causing a problem, but going to 3.17 might). Second, it works on other distros - the Debian family treats https://wiki.debian.org/UnattendedUpgrades as a totally normal supported thing to do, and I don't think Alpine is noticeably less stable than them.

Re:In Praise of Alpine and APK by PhilipRoman on Monday February 20, 2023 @04:19PM (#34873055)
Oh yeah I should have clarified - I use the edge branch for this.
Re:In Praise of Alpine and APK by yjftsjthsd-h on Monday February 20, 2023 @05:04PM (#34873569)
Oh, yeah, in that case I could see it breaking eventually:) Although, it might not be an obvious breakage, either; you wouldn't notice something like upstream removing a package that you have installed (ask me how I know).
Re:In Praise of Alpine and APK by zhala on Tuesday February 21, 2023 @10:40AM (#34882337)
We do this regularly in production. We do biweekly container rebuilds, many running alpine and installing version unpinned packages. So far very few (if any) actual issues with that. We do of course do smoketests prior to promoting to production.