Skip to content

Commit

Permalink
manifest: drop containernetworking-plugins and podman-plugins
Browse files Browse the repository at this point in the history
Since podman is dropping support for CNI networking entirely
we can drop containernetworking-plugins and  podman-plugins.
Podman stopped shipping podman-plugins rpm with the Podmanv5.
Subsequently, we wouldn't need containernetworking-plugins as
it is just libraries for writing CNI plugins.
Ref: coreos/fedora-coreos-tracker#1629 (comment)
  • Loading branch information
gursewak1997 committed Feb 13, 2024
1 parent 533a824 commit ee0ac0f
Showing 1 changed file with 3 additions and 4 deletions.
7 changes: 3 additions & 4 deletions manifests/fedora-coreos-base.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -104,11 +104,10 @@ packages:
# Containers
- systemd-container catatonit
- fuse-overlayfs slirp4netns
# support for old style CNI networks and name resolution for
# podman containers with CNI networks
# Some host applications((podman,NetworkManager, etc) ) use
# dnsmasq as the binary for some various utility operations.
# https://github.com/coreos/fedora-coreos-tracker/issues/519
# https://github.com/coreos/fedora-coreos-tracker/issues/1128#issuecomment-1071338097
- containernetworking-plugins podman-plugins dnsmasq
- dnsmasq
# For podman v4 netavark gets pulled in but it only recommends
# aardvark-dns (which provides name resolution based on container
# names). This functionality was previously provided by dnsname from
Expand Down

0 comments on commit ee0ac0f

Please sign in to comment.