From: MBB <mbbert@gmail.com>
To: ~alpine/users@lists.alpinelinux.org, Sertonix <sertonix@posteo.net>
Subject: Re: Diskless systems do not boot with latest apk versions from cache
Date: Sun, 02 Feb 2025 16:16:03 +0100
Message-ID: <2408933.iZASKD2KPV@ntb-norbert>
Organization: Private
In-Reply-To: <2324387.irdbgypaU6@ntb-norbert>
References: 
 <9410103.CDJkKcVGEf@ntb-norbert> <2700244.k3LOHGUjKi@ntb-norbert>
 <2324387.irdbgypaU6@ntb-norbert>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"


Am Sonntag, 2. Februar 2025, 09:11:22 Mitteleurop=C3=A4ische Normalzeit sch=
rieb MBB:
> Am Samstag, 1. Februar 2025, 14:39:34 Mitteleurop=C3=A4ische Normalzeit s=
chrieb MBB:
> > Am Samstag, 1. Februar 2025, 13:12:29 Mitteleurop=C3=A4ische Normalzeit=
 schrieb Sertonix:
> > > On Sat Feb 1, 2025 at 9:24 AM CET, MBB wrote:
> > > > Hi all!
> > > >
> > > > I have 3 Raspberry Pis, different PI versions and different Alpine =
versions (3.18.9, 3.19.1, 3.19.4).
> > > >
> > > > All have the same issue.=20
> > > >
> > > > I'm doing:=20
> > > > apk update; apk upgrade
> > > >
> > > > Checking the version of an upgraded binary before reboot, e.g. name=
d, looks ok.
> > > >
> > > > After reboot, it loads an old version even though a newer package i=
s available in cache.
> > > >
> > > > gate [/etc/apk]$ ls -al cache
> > > > lrwxrwxrwx    1 root     root            22 Feb  1 08:50 cache -> /=
media/mmcblk0p1/cache
> > > >
> > > > gate [/etc/apk/cache]$ ls -altr bind-9*
> > > > -rwxr-xr-x    1 root     root        207297 Mar 15  2024 bind-9.18.=
24-r1.5aca84cc.apk
> > > > -rwxr-xr-x    1 root     root        208996 Dec 17 16:37 bind-9.18.=
32-r0.1254446d.apk
> > > > -rwxr-xr-x    1 root     root        209078 Jan 29 19:44 bind-9.18.=
33-r0.b6697cb2.apk
> > > >
> > > > gate [/etc/apk/cache]$ named -V
> > > > BIND 9.18.32 (Extended Support Version) <id:d1f1392>
> > > > running on Linux armv7l 6.6.14-0-rpi #1-Alpine SMP Fri Jan 26 13:40=
:47 UTC 2024
> > > >
> > > > Is there something I'm doing wrong?
> > >=20
> > > It looks correct what you are doing. Could you try if running this
> > > commands returns any error?
> > >=20
> > > $ apk --simulate add bind=3D9.18.33-r0 --no-network
> >=20
> > No errors with this command.
> >=20
> > *gate [*~*]$ *doas apk --simulate add bind=3D9.18.33-r0 --no-network=20
> > doas (norbert@gate) password: =20
> > (1/5) Upgrading bind-libs (9.18.32-r0 -> 9.18.33-r0)=20
> > (2/5) Upgrading bind-tools (9.18.32-r0 -> 9.18.33-r0)=20
> > (3/5) Upgrading bind-dnssec-root (9.18.32-r0 -> 9.18.33-r0)=20
> > (4/5) Upgrading bind (9.18.32-r0 -> 9.18.33-r0)=20
> > (5/5) Upgrading bind-openrc (9.18.32-r0 -> 9.18.33-r0)=20
> > OK: 157 MiB in 215 packages
>=20
> I removed all outdated bind packages from the cache with the result, that=
 bind is no longer available after reboot.
> After moving the bind*9.18.32-r0*.apk files back into the cache directory=
, the service gets restored and starts up without issues after reboot.
>=20
> It seems that something's pointing to a specific version.
>=20

`apk cache sync` breaks the entire system.=20

This cleans the cache from outdated APKINDEX* and *.apk files.=20
But after reboot nothing is loaded and the boot process ends with a `(none)=
 local:` prompt.

Restoring the old cache directory, brings the system to life again.

Same issue when I manually delete only the APKINDEX* files, and update the =
local DB with `apk update` to download fresh APKINDEX.

Restoring the old APKINDEX* files from a backup fixes this.

> > >=20
> > > > BR
> > > > Norbert
> > >=20
> > >=20
> >=20
> >=20
>=20