Skip to content

Release Notes

November 2021 (version 7.8)


This release adds a major improvement to DietPi, providing our own official DietPi-Dashboard to both monitor and manage your DietPi installations. It also brings full support to latest launches: Raspberry Pi Zero 2 W and Radxa Zero SBCs - two powerful and ultra small SBC variants!

New Software

  • DietPi-Dashboard We are proud to announce official DietPi Web interface for monitoring and managing your DietPi system using your web browser ! You can see various statistics, and even run commands in the console embedded in the web page! Thanks to the great work of @ravenclaw900!

    DietPi-Dashboard Screenshot


    It is still in beta phase as we test and gradually implement more features. We hence do not recommend yet to actively use in on sensitive production systems.

    We would be happy if you would try it to install, either using dietpi-software or running the command in the console:

    dietpi-software install 200

    Please share your feedback! You can find more details in the original GitHub issue: MichaIng/DietPi#448

New supported SBCs

  • Radxa Zero DietPi offers support for this tiny Quad Core SBC. It has the same form factored as Raspberry Pi Zero, but way more powerful. This SBC has been added to DietPi with the hardware ID 74. Many thanks to @almirus and @dhry for helping with testing and debugging an early image: MichaIng/DietPi#4831

    DietPi Radxa Zero Photo

  • Raspberry Pi Zero 2 W The Raspberry Pi Zero 2 W brings increased processing power. According to Raspberry, multithreaded chores are up to five times faster, which is a significant boost, while keeping exactly the same form factor.

    Raspberry Pi Zero 2 photo

    With this release, the initial DietPi support for this Raspberry Pi Zero / Zero W successor has been added. It also comes with overclocking profiles, helpful to achieve even better performance. It uses hardware ID 3 (shared with RPi 3/3+, since this version has the same processor as the original Raspberry Pi 3).

    Many thanks to @CassTG for providing the early hardware information and doing intensive overclocking tests.


  • DietPi-Backup

    • A feature has been added to enable daily system backup via cron job. Many thanks to @Lycidias93 for suggesting this feature: MichaIng/DietPi#3871DietPi Backup Daily

    • Rsync / Transfer logs are now done to dietpi-backup.log inside of the backup directory. This way they remain persistent even if DietPi-RAMlog is enabled and can be reviewed at a later time. This is helpful especially when daily backups via cron job are enabled, where the log obviously is not presented directly when the backup finished. A related option to review the last transfer log has been added to the dietpi-backup main menu. The old log file /var/log/dietpi-backup.log is moved to the new location, if any backup exists during next DietPi update.

    • When using an NFS mount as backup target, it is now verified that the NFS share supports UNIX permissions to prevent the creation of a broken system backup in the first place.
  • DietPi-Config

    • Overclocking profiles for most Raspberry Pi models have been updated to match the effective 100 MHz ARM/CPU frequency steps used by current firmware.
    • An energy saving profile has been added to some models, which reduces minimum and maximum voltage a little, reducing energy consumption and heat emission a little on idle and on load. DietPi Overclocking Profiles
    • The option to prefer IPv4 connections when IPv6 is enabled has been removed: This only worked for APT and wget, while e.g. cURL and ping were never affected by this setting, which meant an inconsistent behaviour. If one faces issues with IPv6 enabled, it should be simply disabled instead of preferring/forcing IPv4 only for specific tools.
  • DietPi-Drive_Manager

    • When transferring the DietPi user data to a different drive, it is now checked whether the target location is located within a supported filesystem type, one with native symlink and UNIX permission support. The same is done when using the CLI script /boot/dietpi/func/dietpi-set_userdata.
    • Transferring the root filesystem is now supported on Odroid C4/HC4 models.
    • The option to transfer the root filesystem is now shown as well when the drive does not contain any filesystem. The process implies formatting with a supported filesystem anyway which makes the condition obsolete. Also it is not needed anymore to unmount the filesystem manually first, as this is done automatically before formatting. In the related format menu, only supported filesystems are listed, i.e. ext4 and additionally F2FS on Raspberry Pi. The input box to enter a custom mount point is omitted as it is only temporarily used until the root filesystem transfer has finished. The swap file is not disabled anymore as it can be copied and reused as is on the new root filesystem without issues.
    • When transferring the root filesystem, further checks are performed: There needs to be a dedicated boot partition (required on Raspberry Pi and default on our current Odroid images), as this is what the transfer steps expect and the only reason for moving only the root filesystem instead of cloning the whole drive or flashing the DietPi image to an external drive in the first place. The expected boot/kernel configuration files need to be present so that the kernel can be instructed to mount the new root filesystem. The DietPi user data must not currently be located at the target partition as it would be formatted and all data hence lost.
    • On ext4 filesystems, the reserved blocks percentage is now shown and can be changed as well if the drive is not currently mounted.
  • DietPi-RAMlog The /var/log directory structure is now synced to the persistent disk storage after software installs and via daily cron job to prevent missing logs files or directories in case of unclean shutdowns, which usually lead to failing service startups.

  • DietPi-Software | Roon Server Added support for the new .NET core based version, released on November 3rd, which is expected to have improved performance compared to the old Mono based version. To resolve an old issue with our Roon Server implementation (see below), a reinstall is done during the DietPi update, which pulls in the .NET core dependencies as well. But this will NOT update the Roon Server version to prevent issues with potentially required migration steps. After updating DietPi, use Roon’s internal updater to benefit from the new version.

Bug Fixes

  • Raspberry Pi Worked around an issue on Raspberry Pi ARMv6/7 Bullseye systems where some software failed to start, e.g. RealVNC, if binaries were compiled against an older libraspberrypi0 version with different shared library names.
  • DietPi-Drive_Manager Resolved an issue where resizing F2FS filesystems failed when currently mounted. Contradicting the docs and error output, mounting the filesystem read-only is not sufficient, but it needs to be unmounted instead, which is now done automatically before the resize and remounted afterwards.
  • DietPi-Drive_Manager Resolved an issue where resizing ext4 filesystems could have failed when not currently mounted. Especially if the drive is newly attached, a full fsck needs to be done once before it can be resized. This is now done automatically, allowing to resolve filesystem errors interactively, before resizing an offline ext4 filesystem.
  • DietPi-Config Resolved an issue where Raspberry Pi 4 overclocking profiles were offered on Raspberry Pi 400. A new set of profiles have now been added dedicated for the Raspberry Pi 400.
  • DietPi-Software | IceCast Resolved an issue where a new install failed due to an attempted operation on a non-existing file. Many thanks to @killtux for reporting this issue: MichaIng/DietPi#4858
  • DietPi-Software | Logitech Media Server Resolved an issue where the uninstall failed as the package postinst script tried to remove the service user before the service was stopped.
  • DietPi-Software | Roon Server Resolved an issue where the internal updater purged all Roon Server data and configs, since the data directory was located within the install directory. Roon Server will now be installed to /opt/roonserver while the data directory remains at /mnt/dietpi_userdata/roonserver. This change will be applied via DietPi update as well, your data and configs will remain untouched. Many thanks to @JanKoudijs for reporting this issue and providing a solution: MichaIng/DietPi!4897
  • DietPi-Software | LXDE Resolved an issue where on some cases on first desktop start, desktop icons were missing and another issue on Bullseye systems, where a No session for pid error message popped up on desktop start. Many thanks to @kerryland for reporting these issues: MichaIng/DietPi#4914
  • DietPi-Software | LXDE Resolved an issue where the Firefox browser panel icon was present even if no Firefox was installed. In this case now either Chromium or the text editor is added as replacement.
  • DietPi-Software | Home Assistant Resolved an issue where the install failed on ARMv6/ARMv7 Bullseye systems.
  • DietPi-Software | Tor Relay This software option has been disabled on Stretch. The Tor package shipped by the Debian Stretch repository is too old to support required protocols of the Tor network, when running a relay. Many thanks to @cptechnik for reporting this issue: MichaIng/DietPi#4925
  • DietPi-Software | Deluge Resolved an issue where on fresh installs the services failed due to an invalid config file syntax. Many thanks to @bookedirl for reporting this issue.
  • DietPi-Software | Deluge As the package from Raspbian Bullseye currently fails, we needed to disable Deluge for Raspberry Pi systems with ARMv6 Bullseye image. The bug has been reported to the Raspbian maintainers and we hope for a fix until next DietPi release: MichaIng/DietPi#4944
  • DietPi-Software | Lighttpd Resolved an issue where reinstalls on a Bullseye system with DietPi-LetsEncrypt used, erroneously enabled an SSL configuration which could prevent the service start.

As always, many smaller code performance and stability improvements, visual and spelling fixes have been done, too much to list all of them here. Check out all code changes of this release on GitHub: MichaIng/DietPi!4951

Removed Software

  • Subsonic Since it is not developed anymore and due to shared library dependencies only compatible with Debian Stretch, we removed Subsonic from DietPi-Software. With Airsonic-Advanced, we’ll provide a well maintained and Bullseye-compatible alternative soon. If you currently have Subsonic installed, it will remain. If you want to uninstall it, follow the instructions here: MichaIng/DietPi!4895
  • emonHub Since we do not have a single reported installation, we removed emonHub from DietPi-Software. If you currently have emonHub installed, it will remain. If you want to keep using and updating it, have a look at the official repository at openenergymonitor/emonhub. If you want to uninstall it, follow the instructions here: MichaIng/DietPi!4895

Removed Supported SBC

  • Odroid N1 There is not a single reported DietPi Odroid N1 system, which makes sense as this model was never really released. Only a small number of developer samples are floating around, not worth to keep maintaining an image and dedicated code. If there are unreported Odroid N1 DietPi systems out there, they will be automatically migrated to the Generic Rockchip RK3399 device ID on DietPi update.