Hi,

I use this script
https://github.com/jmarcgit/rpi-alpine-update/blob/main/rpi-alpine-update.sh
to automate updates on a RPI. It's run from cron, every week.

Yesterday it failed during the 3.24.1 update but I don't have any log files
to help identifying the issue

   - my system is diskless
   - latest-stable branch
   - I use iproute2 to set an ipv6  token when starting the network (pre-up
   ip token set command in /etc/network/interfaces)
   - the script runs this for packages upgrade: apk update && apk upgrade
   && apk cache sync && lbu commit

What happened is that iproute2 wasn't available and therefore the ip token
command failed (busybox command was used as a fallback) and as a result the
network didn't work anymore.

I moved the RPI to my desk and after restoring the network interface, I was
able to run the upgrade sucessfully.

Do you see why the fact that the network interface is depending on iproute2
could be a problem during a release upgrade ?

You should check the results of apk update/upgrade and act accordingly in
your scripts.

I had problems in the past, where a package was not fetched due to an
intermitent network error.

Your system is diskless, likely we will never know the true cause of the
error.

Regards,

Fabio Martins

(+5521) 97914-8106 (Signal)
https://www.linkedin.com/in/fabio1337br/

On Sun, 14 Jun 2026 at 12:20 Jerome Marc <marcgruselle@gmail.com> wrote:

> Hi,
>
> I use this script
> https://github.com/jmarcgit/rpi-alpine-update/blob/main/rpi-alpine-update.sh
> to automate updates on a RPI. It's run from cron, every week.
>
> Yesterday it failed during the 3.24.1 update but I don't have any log
> files to help identifying the issue
>
>    - my system is diskless
>    - latest-stable branch
>    - I use iproute2 to set an ipv6  token when starting the network
>    (pre-up ip token set command in /etc/network/interfaces)
>    - the script runs this for packages upgrade: apk update && apk upgrade
>    && apk cache sync && lbu commit
>
> What happened is that iproute2 wasn't available and therefore the ip token
> command failed (busybox command was used as a fallback) and as a result the
> network didn't work anymore.
>
> I moved the RPI to my desk and after restoring the network interface, I
> was able to run the upgrade sucessfully.
>
> Do you see why the fact that the network interface is depending on
> iproute2 could be a problem during a release upgrade ?
>
>