github MichaIng/DietPi v10.8

5 hours ago

New tools

  • dietpi-wireguard | This new tool manages WireGuard servers and their clients via menu or command line: create servers and clients, show client configs as QR code, disable, enable and remove clients, change their settings, and the server port, address and IPv6. It works with the existing configs in /etc/wireguard, hence also for servers which were not installed via dietpi-software. The latter creates its server config via dietpi-wireguard init now, and no client anymore. New servers get an IPv6 subnet (NAT66) and IPv6 forwarding, so that clients can use IPv6 through the VPN, which did not work with the previous config. Existing servers can turn IPv6 on via dietpi-wireguard. Disabling IPv6 via dietpi-config turns it off for WireGuard servers, as they could not start otherwise. Many thanks to @Vansinnet for doing for requesting this feature: #3100

Enhancements

  • Quartz64 | Support for ATAPI/SCSI CD/DVD/Blu-ray drives, and the ISO format with common extensions, have been added to our kernel builds. Many thanks to @NoProblemsHere for suggesting this: https://dietpi.com/forum/t/25511
  • dietpi-config | The option to change the system hostname has been moved from "Security Options" to the better fitting "Network Options: Misc" submenu. Many thanks to @ikem-krueger for doing this suggestion: #7218
  • dietpi-config | Added a "Time sync timeout" setting next to "Time sync mode", stored as CONFIG_TIMESYNC_TIMEOUT in dietpi.txt (default: 60 seconds). Many thanks to everyone who reported and discussed this: #6684
  • dietpi-network | It is now possible to create a static interface configuration without gateway via CLI. Previously, a default gateway value was assigned, if none was passed explicitly via CLI.
  • dietpi-network | Virtual interfaces from Docker and other container engines are now hidden in the menu on the host side.
  • dietpi-software | Software IDs are now named instead of numeric, e.g. "nodered" instead of 122, derived from the software name in lower case with all dashes, dots, underscores, spaces and other special characters removed. This applies to the CLI, the search menu, AUTO_SETUP_INSTALL_SOFTWARE_ID in dietpi.txt, /boot/dietpi/.installed, and the dietpi-survey upload. Input is normalised the same way, so "Node-RED" is accepted. Numeric IDs are still accepted everywhere, and existing /boot/dietpi/.installed files are migrated. The dietpi-software free command has been removed, as IDs are unique by name.
  • dietpi-software | HAProxy: We provide own HAProxy DEB package via our APT server now. A source build on (re)install, and related build dependencies, are hence not required anymore, and update are applied via apt upgrade. We additionally hardened our default config, letting workers run as dedicated haproxy system user, and applying some sandboxing to the systemd service. And existing /etc/haproxy/haproxy.cfg is not touched, and we generally aim to keep our package widely compatible with Debian's package. Users who did previously install HAProxy via apt from Debian instead of dietpi-software, will receive this package upgrade as well. Please let us know if you face any issues or incompatibilities with this. Our additional sandboxing should not cause any breakage, but possible that we missed something. And our package ships the latest release, while Debian is some subversions behind, even in testing and unstable, at time of writing. Many thanks to @gitzjoey for reporting that our default config did let works run unnecessarily as root: https://dietpi.com/forum/t/25490

Bug fixes

  • UTM VMs | Our appliance configuration has been updated for ARM and UEFI support. Previously, a wrong architecture string was used for ARM, UEFI boot was always disabled, and outdated virtual hardware was used. The new config uses VirtIO hardware where available. Very old UTM versions might not be able to import these new appliances. Let us know if this is the case for you, and updating UTM is not possible for some reason. Many thanks to @oxoocoffee for reporting this issue, and testing new appliances on Apple Silicon hosts: #8317
  • dietpi-drive_manager | Resolved an issue where formatting a drive with HFS+ failed on Debian Trixie and later, as the legacy HFS non-plus hfsutils package was attempted to be installed, which is not available anymore since Debian Trixie. Many thanks to @k8seren for reporting this issue: #8328
  • dietpi-drive_manager | Resolved an issue where NFS exports with spaces in their share path were shown truncated in the export list, and could not be permanently mounted when entering the path manually. Spaces in exported shares are now correctly handled and shown in the exports list, and encoded as \040 in /etc/fstab entries, like it was done for Samba/CIFS shares already. Many thanks to @thr-4 for reporting this issue: #8332
  • dietpi-network | Resolved an issue where changes to WiFi hotspot settings (SSID, key, frequency, channel, and WiFi standards) were instantly reverted in the interface menu, since they were reloaded from the config files whenever the menu was redrawn. Changes are now kept until saved or applied. Many thanks to @Zoatebix for reporting this issue: #8335
  • dietpi-network | Resolved an issue where configuring a network interface as hotspot still caused wpa_supplicant to start, which broke the hotspot if it succeeded to connect to a network, i.e. if /etc/wpa_supplicant/wpa_supplicant.conf contained credentials for an SSID in range already. Many thanks to @CVBruce for reporting this issue: https://dietpi.com/forum/t/25514
  • dietpi-network | Resolved an issue where no warning was shown when applying a static gateway to an interface while another enabled interface already has a default gateway, which can lead to a missing Internet connection after a reboot. Additionally, dietpi-network apply prints the reason now if it refuses a config without terminal due to such a conflict, and unused gateway lines of DHCP stanzas are not considered a default gateway anymore.
  • dietpi-network | Resolved an issue where a single quote within the proxy username or password caused syntax errors on every interactive bash session start, as it ended the quoted proxy URL in /etc/bashrc.d/dietpi-proxy.sh. Additionally, a colon within the proxy password does not lead to a cut password anymore when proxy settings are changed afterwards.
  • dietpi-network | Resolved an issue where disabling an interface which was still configured in the old /etc/network/interfaces main config was not possible.
  • dietpi-network | Resolved an issue where invalid values were accepted and written to the network configuration, e.g. IP addresses with octets above 255 or a CIDR prefix above 32 and, via the command line, also gateway, DNS, WiFi hotspot SSID, key, channel and interface name values. All input is now validated, in the interface menu and via the command line.
  • dietpi-cloudshell | The DHCP vs static IP state is now correctly detected, if the interface configuration is stored below /etc/network/interfaces.d, as dietpi-network does it.
  • dietpi-software | UrBackup: Resolved an issue where the uninstall failed with "Read-only file system" errors when the backup location contained Btrfs snapshots created by UrBackup, which are read-only subvolumes. If such snapshots are found, you are now asked whether to delete them together with the backups. When skipping, the uninstall continues but the backup location is left untouched. Many thanks to @anika200 for reporting this issue: https://dietpi.com/forum/t/25501
  • dietpi-software | Immich: Resolved an issue where thumbnails of new photos with GPS location were not generated since Immich v3.3, as the metadata extraction failed due to the missing GeoNames country info file, which is now required for reverse geocoding. Existing instances can apply the fix via dietpi-software reinstall immich. Many thanks to @UweDoe for reporting this issue: #8367
  • dietpi-software | Immich Machine Learning: Resolved an issue where the service failed to start due to a missing new submodule. Due to changed Python version requirements, support for Debian Bookworm and Forky needed to be removed. If you run Immich-ML on Bookworm, consider upgradeing to Debian Trixie, following our guide: https://dietpi.com/blog/?p=4014. In a future release, we may restore support for all Debian versions by switching to a uv-managed Python instance, but that has not been decided yet. Many thanks to @nighthawk2111 for reporting this issue: #8356
  • dietpi-software | Tor Relay: Resolved an issue where the local Unbound DNS resolver, applied on exit relay installs, was not stored in the config of static network interfaces managed by dietpi-network. If resolvconf is installed, it was hence replaced by the previous DNS server again on next network restart or reboot. The DNS server is now applied via dietpi-network.
  • dietpi-software | Kubo: Resolved an issue where the installation failed, since the used download server dist.ipfs.tech is not reachable anymore. Builds are now pulled from their official GitHub repository.
  • dietpi-software | Nextcloud: Resolved an issue where the installation failed on Debian Bookworm, since Nextcloud 35 requires PHP 8.3 or higher. On Bookworm, the latest Nextcloud 34 is now installed instead.

Don't miss a new DietPi release

NewReleases is sending notifications on new releases.