How prepare the transition/upgrade from Buster to next version?

Hello,

in any time the next upgrade from Debian (Buster) to the next version, I think the so call next kernel, will occur.

  • What does this mean for DietPi? I guess there will be an upgrade soon after?


  • What is the best way for an end user of DietPie like me to deal with this?

I have stored all my DietPie Userdata to an USB which I have mounted. Does this mean that after installing the next DietPie Version and all the software/servers again that they will run again? I dont think so, because the configurations files of programs are stored in other folders, right?

Or do you use a backup software to store all Config-Files to restore all configurations after installing the software again?

Or is there no way around just install DietPi, all programs and configurations again?

Is there an function within DietPi which simplifies the transition (backup and restore) of configurations, …?

I dont know, but would Docker ease the transition? I dont know if its possible to run all the programs in different containers and if it does make sense.

Thank you.

Hi,

I guess there are a couple of misunderstandings on your side.

in any time the next upgrade from Debian (Buster) to the next version.

The next Debian version is called Bullseye. We expect a release from Debian side mid of 2021

I think the so call next kernel, will occur.

A Linux kernel is something different than a Debian Version like Buster or Bullseye. There are multiple kernel release during a life cycle of a Debain version. There are released time by time https://en.wikipedia.org/wiki/Kernel_(operating_system)

What is the best way for an end user of DietPie like me to deal with this?

No need to rush. We still have users, running Debian Stretch where Buster was released 1,5 years back.

Does this mean that after installing the next DietPie Version and all the software/servers again that they will run again?

A DietPi version has nothing to do with Debian Release or a Kernel Release. DietPi is some set of scripts on top of an operation system. Officially DietPi supports Debian Stretch and Buster. Unofficially, Bullseye should be working as well already. Stretch support will be dropped as soon as Bullseye will be released. But this doesn’t mean Stretch systems will stop to operate. They simply will not receive DietPi script updates anymore from DietPi side.

I guess there will be an upgrade soon after?

DietPi will not force or offer Destro upgrades. Something the user would need to take care. An example how this could look like from Stretch to Buster https://dietpi.com/forum/t/qbittorrent-version-shipping-with-dietpi/2326/9
But as already said. Nothing to rush.

Is there an function within DietPi which simplifies the transition (backup and restore) of configurations, …?

dietpi-backup provides full system backup. It’s not intend for single config files. It always will save your entire system. Restoring a Buster backup on a Bullseye system, will downgrade your system back to Buster

I dont know, but would Docker ease the transition?

Something to check with Docker what and how it is possible

I dont know if its possible to run all the programs in different containers and if it does make sense.

Depends on the availability of Docker images for your applications.

Hello!!

Thank you for the comprehensive information.

As a matter of fact since some years now I have a Raspbian Stretch running with a FEHM-Server (House-Automatic), PiHole and Open Median Vault (Cloud-Service) and some more.

FHEM starts to have some issues so that I will install the OS and all server newly as soon as Bullseye comes out.

That is the reason why I am testing DietPi right now: Lightweight and easy to install. Maybe better than Raspbian?

I don’t have any problem to build up everything again next summer. But I would like to prepare the new installations in a fashion that future transitions would go faster, easier and without faults. In addition I would like to have the opportunity if one server gets messy “to rip it out” and install a new version without compromising the OS and the other servers.

I have heard some things about Docker. But I am not really into it. I do not understand what Docker is about. Might it be a solution for my ‘project’?

What is the best solution for an Code/Linux-Amateur like me getting it done. I guess installing everything new all 3-5 years?

Kind regards!! And thank you!!

Hi,

Maybe better than Raspbian?

If you are running on a Raspberry Pi you are still on Raspberry OS :wink:
DietPi is not an own OS, it’s a set of scripts on top of a base image. However the image was reduced down to a minimum. Means, it’s an extrem slim/diet version of Raspberry OS with some magic scripts around.

since some years now I have a Raspbian Stretch running

well you could clone your SD card to gain a full backup. Once done try to upgrade from Stretch to Buster https://dietpi.com/forum/t/qbittorrent-version-shipping-with-dietpi/2326/9
If thinks are failing, just flash you cloned image back

OK,
well, I am always have a one, two clone backups of my SD-Card. So simply trying to upgrade might be a way.

If an upgrade from stretch to buster works out perfect, how clean will the new installation of the OS Buster and the Servers be? Doing something like this with Windows was/is allays messy.

By the way, how clean are uninstall process in Linux in general? If something was uninstalled, is everything gone? Or is there something left like some registry when done in Windows?

Danke Euch allen! Thank you very much.

So simply trying to upgrade might be a way.

yep, just give it a try :slight_smile:

If an upgrade from stretch to buster works out perfect, how clean will the new installation of the OS Buster and the Servers be? Doing something like this with Windows was/is allays messy.

Not really something you can compare with Windows. At least apt managed packages (Debian repository) will be update one by one to the latest version. Not sure if you are running 3rd party software. There you would need to ensure that this is able to run on Buster as well. Usually not an issue. But that’s why you have the backup/clone SD card :wink:

how clean are uninstall process in Linux in general? If something was uninstalled, is everything gone?

It depends a little bit. Not that I have an example in my head, but sometimes not all files and folder get removed. But in general it’s working fine.

Or is there something left like some registry when done in Windows?

No Linux did not have something like a registry. Everything is based on files and folders.

Bitte gerne, you’re welcome

for updating my dietpi operating system from buster to bullseye. is i have to give these command one by one in terminal windows. if all these commands works then i will enter into bullseye operating system with dietpi

sed -i 's/buster/bullseye/' /etc/apt/sources.list
sed -i 's/buster/bullseye/' /etc/apt/sources.list.d/*.list
apt update
apt upgrade
apt full-upgrade
apt autopurge
/boot/dietpi/func/dietpi-obtain_hw_model
. /boot/dietpi/func/dietpi-globals

any other recommendation ?

Theoretically that could be a way. But you would need to check other source list as well (if applicable) if they would need to be changed as well.

We did some testing with a user who offered to volunteer. There we have seen some challenges on MariaDB that would need more testing. If you have time, you could read through the update process we did: Stretch => Buster => Bullseye

https://github.com/MichaIng/DietPi/issues/4511

in my amd64 nuc after this commands & restart after that sudo apt-get update comand give this result

root@DietPi:~# sudo apt-get update
Err:1 http://ftp.us.debian.org/debian bullseye InRelease
  Temporary failure resolving 'ftp.us.debian.org'
Err:2 https://downloads.plex.tv/repo/deb public InRelease
  Temporary failure resolving 'downloads.plex.tv'
Err:3 https://deb.debian.org/debian-security bullseye/updates InRelease
  Temporary failure resolving 'deb.debian.org'
Err:4 http://ftp.us.debian.org/debian bullseye-updates InRelease
  Temporary failure resolving 'ftp.us.debian.org'
Err:5 http://ftp.us.debian.org/debian bullseye-backports InRelease
  Temporary failure resolving 'ftp.us.debian.org'
Reading package lists... Done
W: Failed to fetch http://ftp.us.debian.org/debian/dists/bullseye/InRelease  Temporary failure resolving 'ftp.us.debian.org'
W: Failed to fetch http://ftp.us.debian.org/debian/dists/bullseye-updates/InRelease  Temporary failure resolving 'ftp.us.debian.org'
W: Failed to fetch https://deb.debian.org/debian-security/dists/bullseye/updates/InRelease  Temporary failure resolving 'deb.debian.org'
W: Failed to fetch http://ftp.us.debian.org/debian/dists/bullseye-backports/InRelease  Temporary failure resolving 'ftp.us.debian.org'
W: Failed to fetch https://downloads.plex.tv/repo/deb/dists/public/InRelease  Temporary failure resolving 'downloads.plex.tv'
W: Some index files failed to download. They have been ignored, or old ones used instead.
root@DietPi:~#

in my raspberry pi-b2 after this commands & restart after that sudo apt-get update comand give this result

root@DietPi:~# sudo apt-get update
Err:1 https://repo.mosquitto.org/debian bullseye InRelease
  Temporary failure resolving 'repo.mosquitto.org'
Err:2 https://archive.raspberrypi.org/debian bullseye InRelease
  Temporary failure resolving 'archive.raspberrypi.org'
Err:3 http://raspbian.raspberrypi.org/raspbian bullseye InRelease
  Temporary failure resolving 'raspbian.raspberrypi.org'
Err:4 https://deb.nodesource.com/node_12.x bullseye InRelease
  Temporary failure resolving 'deb.nodesource.com'
Reading package lists... Done
W: Failed to fetch http://raspbian.raspberrypi.org/raspbian/dists/bullseye/InRelease  Temporary failure resolving 'raspbian.raspberrypi.org'
W: Failed to fetch https://repo.mosquitto.org/debian/dists/bullseye/InRelease  Temporary failure resolving 'repo.mosquitto.org'
W: Failed to fetch https://deb.nodesource.com/node_12.x/dists/bullseye/InRelease  Temporary failure resolving 'deb.nodesource.com'
W: Failed to fetch https://archive.raspberrypi.org/debian/dists/bullseye/InRelease  Temporary failure resolving 'archive.raspberrypi.org'
W: Some index files failed to download. They have been ignored, or old ones used instead.
root@DietPi:~#

Adguard home web page give this error

Error: control/version.json | Couldn't get version check json from https://static.adguard.com/adguardhome/release/version.json: *fmt.wrapError updater: HTTP GET https://static.adguard.com/adguardhome/release/version.json: Get "https://static.adguard.com/adguardhome/release/version.json": read udp 127.0.0.1:46223->127.0.0.1:5335: read: connection refused | 502

Do the other devices user AdGuard Home for name resolution/ad blocking? Looks like it has an issue to contract the update server.

Does AdGuard Home use Unbound or another local resolver? I see a refused 127.0.0.1:5335 connection. In case check Unbound status:

journalctl -u unbound

both system show this fail display page.
Raspberry pi running. homeasssitant, valutwarden, mqtt broker, zigbee2mqtt, openssh
nuc running : plex, adguard, unbound, wireguard, openssh

unbound, homeasssistant, adguard are in trouble
valut warden lokks ok, adguard screen show error (may be unbound).

in dietpi-config networg adpter static & dns resolver cloudflare 1.1.1.1

As you can see on your first screen print, there is an issue with Mosquitto as there is no Bullseye repository available yet. This we already discovered and a workaround is described on the link I posted above https://github.com/MichaIng/DietPi/issues/4511#issuecomment-877590830

On the 2nd screen the issue is with the repository name for debian-security. On Bullseye it’s called bullseye-security at the moment and not just bullseye. /etc/apt/sources.list you would need to adjust as follow

sed -i 's|bullseye/updates|bullseye-security|' /etc/apt/sources.list

Thanks @Joulinar & @MichaIng With your given hints, I am able to troubleshoot both my machines. I confirm that both my machine migrated to bullseye from buster. All my software works same way no change

Raspbeerry pi B2 > Homeasssistant, MQTT, zigbee2mqtt, valutwarden, openssh
NUC AMD64 > plex, adguard home , unbound 1.13, wireguard, openssh

Thanks for your hard work & expert advises every time.

thx for sharing. Don’t forget to switch Mosquitto to Bullseye once they added the repository. You can watch the repo https://repo.mosquitto.org/debian/dists/

I can confirm the update went without problems on my pi 1B

sed -i 's/buster/bullseye/' /etc/apt/sources.list
sed -i 's/buster/bullseye/' /etc/apt/sources.list.d/*.list
sed -i 's|bullseye/updates|bullseye-security|' /etc/apt/sources.list
sed -i 's/bullseye/buster/' /etc/apt/sources.list.d/*mosquitto*.list
apt update
apt upgrade
apt full-upgrade
apt autopurge
/boot/dietpi/func/dietpi-obtain_hw_model
. /boot/dietpi/func/dietpi-globals

Homeassistant and mosquitto are working.

Hi,

until now, Mosquitto is not providing a Bullseye repository and you are still using Buster package. Don’t forget to adjust source list as soon as Mosquitto offers Bullseye packages

Sorry to chime in on this and hopefully its related

Is it better to convert from Buster to Bullseye or just re-install fresh to Bullseye? I know that would depend on cirtumstances - but is it just as clean to convert Vs re-install?

I’m a little concerned about compatilbity with prior package configs/apps, etc if converting…and also a clean install with clean re-install of apps (then restoring just the configs) seems neater, albiet possibly more work?

Cleanest way might be a fresh install as you probably get rid of software you had installed before but they are not needed anymore. Depending on your setup, I might be a complex way as you need to reconfigure all your software title. From DietPi point of view, we don’t offer any functionality to export/import configurations only. This would need to be done manually. If you have a complex tool landscape, an in-place upgrade might be easier, however could lead to other challenges and needed rework. We already know that MariaDB, Lighttpd and PHP would need attention. There might be more.

It really depends on your preferences and if your are willing debug thinks after an in-place upgrade or if you like to invest time into a reconfiguration after a fresh install.

Whatever way you go, you would need to take your time. Actually there is no need to rush. You could clone your system (if not to large) and try which way would fit better, before playing on your production system.