APT UPDATE / UPGRADE after initial bootup fails

[naphelge]

Describe the bug
RasPI 4 8GB RAM
mynode_raspi45_0-3-34.img.gz
2 TB SSD
After installing img to mem card and initial boot up, user ssh-logs in via terminal and updates and upgrades packages: sudo apt update ; sudo apt upgrade -y

upgrade gets hung up on (3) packages:

1. setting up containder.d

   • after ~15-20 mins the raspi needs to be restarted
     • sudo shutdown -r now
   • after reboot, resume upgrade: sudo apt --configure -a

2. setting up docker-ce

   • after ~15-20 mins, ctrl+c to move on

3. setting up redis-server

   • after ~15-20 mins, ctrl+c to move on

After all other pkgs seemed to set up without hiccup, I tried to run the pkg upgrades one at a time:
sudo apt --configure container.d docker-ce / redis-server

But they all just continue to hang and need to be killed

Expected behavior
I expected the updates / upgrades to run without issue. I assume updating/upgrading via apt on cli should be fine to do and even good practice to ensure pkgs are up-to-date.

Desktop (please complete the following information):

• firefox
• Version 141.0
• but I am not having any webserver issues, just using cli thru ssh initially

MyNode hardware (please complete the following information):

• Device: raspi 4 8 GB
• Version

[mynode-dev]

Can you try to reproduce the issue by doing an upgrade via the MyNode interface? It's possible it's taking a long time because other apps are running using limited IO resources, the SD card may be going bad, and docker can just take a long time to install.

[naphelge]

Can you try to reproduce the issue by doing an upgrade via the MyNode interface?

I find it hard to believe the GUI interface is seriously going to fare better than the cli.

It's possible it's taking a long time because other apps are running using limited IO resources

If IO resources were the issue, then I would think I should see system resources hammering away near full throttle which is not the case while monitoring $ TOP

the SD card may be going bad, and docker can just take a long time to install.

I should have included these details in the original post, but actually I tried the install on 3 different microSD cards and two different Raspi 4s, so I can't see it being a h/w issue, the same issue with 5 different pieces of h/w.

I might actually try running a node in a VM on my arch daily driver to see if it fares any better.

[mynode-dev]

The GUI shuts a lot of things down prior to upgrading, so it can be different. You may also have issues if you do an update, specifically of docker, if no data drive is attached.

I've also seen specific docker versions hang like that, but I have not seen it happen recently.

Top may not show IO issues. I've seen bad brands of flash storage take 5 min to copy a file that takes <2s on a normal system. The CPU is basically doing nothing but waiting on the drive to finish syncing data to disk. It's always a possibility.

[tlindi]

Here is close to dublicate of this and additional debug info

• Update from 0.3.34 to 0.3.40 halts to docker related packages #988

I also feeling that this could maybe relate /cause issues of docker images disappearing on reboot/update and non-starting mempool and btcpayserver sometimes.

[mynode-dev]

It's possible it's related. I commented on the other issue.