Conversation
They were just left stale on the FAT partition after being copied to the rootfs /boot dir. Remove them after copy, and also remove them retrospectively on DietPi update, since they can contain sensitive data.
The whole code block ran only if no overlay was applied yet, but did then loop through overlays already applied. Generally it makes sense to apply the 8GB an A12 overlays where needed as well if there are already other overlays applied. Remove the condition, and set a reboot flag instead, to avoid a reboot (and boot loop) if no changes were done.
and add support for newly added Orange Pi boards
It was fixed for Odroids, while support for new Orange Pis was added.
systemd-timesyncd sometimes gives up for at least ConnectionRetrySec, before retrying to connect to time servers, e.g. if network connectivity has not yet been fully established, on its first attempt. Contradictorily, this has been especially observed when syncing time with the local gateway/router. For some reason, in my personal home network case, even that ConnectionRetrySec is 30 seconds (the default), it times out the full 60 seconds during boot, while a systemd-timesyncd.service restart results in an almost instant sync from second 1 (of our script's loop) on. This might be an edge case, probably related to some special reply of the router's time server when it is just about recognizing the peer and its network state. But in any case, it is much more likely to speed up time sync than aborting an actual sync attempt. In the latter case, the delay would be usually only a fraction of a second.
It is the same situation as with "mount", mawk, and others: "required", but not "essential", and no dependency of any other installed package. While "required" packages are not autoremoved, we better mark them as manually installed, to make clear we need/expect them.
Current container images ship without a network stack, which leaves guests with their own network namespace, like Proxmox LXC, offline: #5204 With the flag set, dietpi-build and dietpi-installer add Dropbear, ifupdown and the DHCP client the scripts already choose to the container package set, write the interfaces base config and enable the network wait at boot. First boot needs no special casing anymore: its package gates apply the network setup and regenerate the Dropbear host keys, and dietpi-network defaults containers to "auto". Guest network containers get Dropbear pre-installed and marked as installed, like regular systems. ___________ * dietpi-build: skip DHCP client if no network stack is installed After isc-dhcp-client was removed from Forky, so that we needed to switch to dhcpcd there, it was accidentally installed on container images as well, though autoremoved again in dietpi-installer. Prevent it from being installed in the first place, if no network stack is installed. Add some comments about which packages are needed on which images, an empty lines as code structure * dietpi-installer: deduplicate network stack package assignments * dietpi-build: install hdparm in dietpi-build already * dietpi-build: give networked container images a suffix and add to ci * changelog: add entry about networked container images Co-authored-by: MichaIng <micha@dietpi.com>
No idea why it was this insane 700 MiB. Final disk usage is ~270 MiB, hence 300 MiB should be sufficient.
Signed-off-by: MichaIng <micha@dietpi.com>
Co-authored-by: MichaIng <micha@dietpi.com>
* Check passed upload script existent/executability right at the start of each script * Do make actually use of the passed script path, rather than hardcoded ."/upload.sh" * The upload script is not passed to dietpi-imager if an individual VM image/appliance was requested, since the raw image servers solely as basis for qemu-img to generate the virtual disk image. But adjust logic so that the passed upload script is used for uploads of the final VM image/appliance. * Do not rename Proxmox image anymore. The QCOW2 image can be used with various other virtualizers, and the file extension is sufficient to indicate what it is. Rename the variant option accordingly. * Do not xz-compress QCOW2 images anymore. It reduces the size by a few MiB only, since we use native QCOW2 compression already. That saves users from doing an extra step. * Single-quote workflow expressions in shell context, and add ARMv8 VMs to CI
All rockchip-rk3568-* overlays start with rockchip-rk3568-hk-*, and we use the latter in all other cases.
…tomation platform (#8277) Co-authored-by: MichaIng <micha@dietpi.com>
Co-authored-by: MichaIng <micha@dietpi.com>
MichaIng
marked this pull request as ready for review
September 2, 2026 22:33
Signed-off-by: MichaIng <micha@dietpi.com>
systemd-timesyncd does not remove it on startup.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Beta v10.7.1
(2026-09-02)
New images since v10.7.0
New software since v10.7.0
Enhancements since v10.7.0
/boot/dietpi/func/run_ntpdhas been renamed to/boot/dietpi/func/dietpi-timesync, for consistency, and since it does not make use of thenptdtools anymore since years. When time is synced, it does now restartsystemd-timesyncd.service, to force a fresh connection attempt to the time servers in any case. Especially when the service starts during boot, it has been observed to give up for a while, if network connectivity has not been fully established yet./boot/dietpi/func/dietpi-timesyncis called at a later boot stage, and in the context of thedietpi-updatecheck preceded by a general network connectivity check, so thatsystemd-timesyncdis more likely able to connect to time servers immediately. This change may hence speed up, or even avoid the timeout abortion of the initial time sync at boot, and following DietPi and APT update checks, if enabled.Bug fixes since v10.7.0