Package: netavark Severity: important X-Debbugs-Cc: deb...@hachi.kuiki.net Dear Maintainer,
I notice while reading documentation of podman/netavark at: https://docs.podman.io/en/latest/markdown/podman-network-create.1.html#ipam-driver-driver "When using the netavark backend the netavark-dhcp-proxy.socket must be enabled in order to start the dhcp-proxy when a container is started" The binary is shipped, but the systemd socket and service are not. https://packages.debian.org/sid/amd64/netavark/filelist As such the requested operation doesn't work systemctl enable --now netavark-dhcp-proxy.socket Failed to enable unit: Unit netavark-dhcp-proxy.socket does not exist The other network driver for podman, CNI, does ship an equivalent socket and service, and that does work. https://packages.debian.org/sid/amd64/containernetworking-plugins/filelist I believe the system information below is not applicable to the situation, and isn't even a machine with the package installed, but I don't know if debian bug system requires it... so I'm leaving it in Thank you Jonathan Steinert (hachi) -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 6.8.12-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages netavark depends on: ii libc6 2.38-13 ii libgcc-s1 14-20240330-1 Versions of packages netavark recommends: pn aardvark-dns <none> netavark suggests no packages.
