Am 10.04.2021 um 17:11 schrieb Helmut Grohne:
On Sat, Apr 10, 2021 at 12:17:24PM +0200, Michael Biebl wrote:
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.
Hi Michael,
On Sat, Apr 10, 2021 at 12:17:24PM +0200, Michael Biebl wrote:
> 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
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
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
4 matches
Mail list logo
