How to install on Debian 12, why so recent libc?..

[tbone2k-git]

Hello everyone! o)

I read through several issues here regarding "macvlan" and getting DHCP to work. I currently use netavark v1.4.0 on my Debian 12 test setup. That version is from the regular Bookworm channel.

>apt policy netavark
netavark:
  Installed: 1.4.0-3
  Candidate: 1.4.0-3
  Version table:
     1.14.0-2 650
         650 http://deb.debian.org/debian testing/main amd64 Packages
         600 http://deb.debian.org/debian unstable/main amd64 Packages
  *** 1.4.0-3 700
         700 http://deb.debian.org/debian bookworm/main amd64 Packages
         100 /var/lib/dpkg/status

It seems version 1.14.0 of netavark is availabe in "testing" channel already, so I tried installing from there, but the installation fails, because of not meeting "clib6" version. Is there a need to compile netavark with a clib version recent like this? I had this problem with other packages in the past as well, some projects lower their compilation target and thing can be used on current Debian no problem afterwards.

> apt install netavark/unstable
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Selected version '1.14.0-2' (Debian:testing, Debian:unstable [amd64]) for 'netavark'
Selected version '2.41-6' (Debian:testing, Debian:unstable [amd64]) for 'libc6' because of 'netavark'
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 libc-bin : Depends: libc6 (< 2.37) but 2.41-6 is to be installed
            Recommends: manpages but it is not going to be installed
 libc6 : Breaks: base-files (< 13.3~) but 12.4+deb12u10 is to be installed
 systemd-sysv : PreDepends: systemd but it is not installable
                Recommends: libpam-systemd but it is not going to be installed
                Recommends: libnss-systemd but it is not going to be installed
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
root@250125-debian-base:~# apt install netavark/testing
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Selected version '1.14.0-2' (Debian:testing, Debian:unstable [amd64]) for 'netavark'
Selected version '2.41-6' (Debian:testing, Debian:unstable [amd64]) for 'libc6' because of 'netavark'
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 libc-bin : Depends: libc6 (< 2.37) but 2.41-6 is to be installed
            Recommends: manpages but it is not going to be installed
 libc6 : Breaks: base-files (< 13.3~) but 12.4+deb12u10 is to be installed
 systemd-sysv : PreDepends: systemd but it is not installable
                Recommends: libpam-systemd but it is not going to be installed
                Recommends: libnss-systemd but it is not going to be installed
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.

I am not a professional Linux and package dependency resolver, please don't mind my naive question! o)
I was very happy that I got the most recent podman and pasta versions running on Debian 12 now, until I discovered, that DHCP for macvlan containers does not work.

So I have all the recent versions in place, they all work, but netavark requires more "recent" clib and cannot be combined with the other recent components. This kind of ruins all my efforts! o)

Maybe there is something you can do about it?

Thank you in advance!

ps: During my podman journey I got the feeling that using podman is like surfing on bleeding edge releases and fixes all the time, to get things working I expect to work. The podman ecosystem is not as stable and matured as you would think?

I don't know if sailing with Docker would be more smoothly?! I kind of doubt it and I actually like podman better, because it's nearer to Kubernetes. I also have little motivation to redo all the things with Docker and see how I end up. Setting up this container business is kind of nerve wrecking (for a newbie like me at least o)! Thank you! o)

[Luap99]

This isn't really a upstream issue, we have no control over how the debian packages are build. My understanding is that testing packages are not really meant to work on the stable version.

In general if you like the latest package you could directly switch to debian testing which is updated often. The point of debian stable is to not update packages.

Your other alternative is to build netavark from source.

[tbone2k-git]

Hello! o)
Mhh, ok, thank you! o)

So, maybe I try to get the most recent netavark version from some of the other repositories I already have in use? But this is getting quite messy to be honest, not sure this is the right way to go. As already mentioned, using recent Podman components is kind of an experiment it seems, what is it I do wrong, that only the most recent components do what I had in mind?

Maybe I rephrase my actual target: How to get a separate IP for the services I have setup in a compose.yml?
Is this possible with netavark v1.4 or do I really need the most recent v1.14.x releases for this to work?

I already switched to "pasta" because "slirp4netns" is kind of deprecated in recent Podman 5+. It caused quite some hickups already and I don't seem to get any closer to my Podman container lab, there's always something which does not work (yet) or only with some kind of fix not available.

No offense, you do a great job, I could not do anything of what you do! o)