Hi all,
I ran into a networking problem after reconfiguring from an older
generation to a recent one, and I think I've traced it to a version
mismatch, but wanted to check with the list before assuming that's the
whole story.
Going from guix commit 115e109 (May 18) to aa7a1c8 (Jul 20), podman got
bumped from 5.8.2 to 6.0.1. netavark stayed at 1.14.1 across both
generations though. Upstream's podman 6.0 release notes say it needs to
be paired with netavark 2.0.0, so this looks like podman moved ahead
without netavark following.
What I'm seeing in practice: I run a few containers through
oci-service-type, each with its own oci-network-configuration. After the
reconfigure, the existing network files stopped parsing:
Error: netavark: failed to load network options: IO error: invalid
type: sequence, expected a map at line 1 column 137
And trying to recreate a network from scratch fails differently, both
from the Shepherd-generated podman-networks-create.scm service and from
running it by hand:
$ podman network create volname
error: unrecognized subcommand 'create'
Usage: netavark [OPTIONS] <COMMAND>
Error: netavark: : EOF
netavark's own CLI doesn't have a `create` subcommand as far as I can
tell (that's part of the plugin API, not netavark core), which is why I
suspect podman 6.0.1 is talking to it as if it were the 2.0 interface.
`podman info --format '{{.Plugins.Network}}'` just shows the normal
[bridge macvlan ipvlan], so it doesn't seem to be a plugin path issue on
my end.
Has anyone else run into this? Any advise? Also curious whether there's
a cleaner way to pin just podman/netavark/aardvark-dns back to their May
versions while the rest of the system stays current, rather than rolling
back the whole generation.
Thanks for any pointers.
Best, Diego
