Skip to content

Ubuntu: Podman networks should not be used by crio when both podman and crio are installed #95

@ggiguash

Description

@ggiguash

When both podman and crio are installed, some MicroShift pods are using the "wrong" network defined by podman.

Oct 20 13:42:09 runnervmzdgdc crio[47435]: time="2025-10-20T13:42:09.636785474Z" level=info msg="Found CNI network podman (type=bridge) at /etc/cni/net.d/87-podman-bridge.conflist"
Oct 20 13:42:09 runnervmzdgdc crio[47435]: time="2025-10-20T13:42:09.636810611Z" level=info msg="Updated default CNI network name to podman"
Oct 20 13:43:23 runnervmzdgdc crio[47435]: time="2025-10-20T13:43:23.435150831Z" level=info msg="Adding pod openshift-service-ca_service-ca-7b9c4f5976-wmf9r to CNI network \"podman\" (type=bridge)"

Oct 19 16:03:46 runnervmzdgdc crio[46851]: time="2025-10-19T16:03:46.054552461Z" level=info msg="Adding pod cert-manager_cert-manager-cainjector-589dc747b5-dt4wf to CNI network \"podman\" (type=bridge)"

Oct 19 16:04:13 runnervmzdgdc crio[46851]: time="2025-10-19T16:04:13.476615763Z" level=info msg="Found CNI network kindnet (type=ptp) at /etc/cni/net.d/10-kindnet.conflist"

Need to make sure /etc/cni/net.d/ only contains kindnet CNI definition.

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions