Am 08.04.21 um 22:24 schrieb Helmut Grohne:
Package: systemd
Version: 247.3-3
Tags: bookworm sid

systemd used to include systemd-timesyncd. Now it is split out to a
separate binary package. Thanks. However, systemd now depends on
systemd-timesyncd, so we cannot really remove it (unless installing
something like ntp). For containers, having a time-daemon is not useful
and we want to reduce the filesystem as much as possible. Therefore it
would be good to reduce the dependency to Recommends.

A few thoughts.
The disk footprint of systemd-timesyncd is rather small.
It would be good to know which kind of containers your have in mind.
docker-style (minimal) without an init or with a full-blown init like lxc (fat)? The former doesn't have init/systemd installed (and thus no systemd-timesyncd), the latter does and systemd itself is much bigger disk footprint wise.

If we bump the prio of systemd-timesyncd, those minimal containers will now suddenly get systemd-timesyncd by default (which in turn pulls systemd). So this would be a regression. You'd have to be careful to omit systemd-timesyncd when building the container image.

For fat containers, having systemd-timesyncd installed doesn't really gain you a lot (and is no regression compared to buster, where it was folded in). Runtime-wise, having systemd-timesyncd installed, is not a problem either, as systemd-timesyncd.service has ConditionVirtualization=!container


Michael


Attachment: OpenPGP_signature
Description: OpenPGP digital signature

Reply via email to