# Docker CE breaks KVM bridged networking

**URL:** <https://forums.rockylinux.org/t/docker-ce-breaks-kvm-bridged-networking/11806>\
**Category:** Rocky Linux Help & Support\
**Created:** [November 9, 2023, 6:57am UTC](https://forums.rockylinux.org/t/docker-ce-breaks-kvm-bridged-networking/11806 "2023-11-09T06:57:32Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![microlinux](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/microlinux/32/1244_2.png) [@microlinux](https://forums.rockylinux.org/u/microlinux)\
**Post date:** [November 9, 2023, 6:57am UTC](https://forums.rockylinux.org/t/docker-ce-breaks-kvm-bridged-networking/11806/1 "2023-11-09T06:57:32Z")

</div>

Hi,

I’m running Rocky Linux 8 on my main workstation. For testing purposes I’m using KVM/`libvirt` since it performs much better than VirtualBox.

I just installed Docker CE from the official Docker repository and found out that this breaks KVM networking. I’m using a `br0` bridge for KVM, and when I start Docker, all KVM hosts become unreachable.

After googling “`docker breaks kvm bridge`” I found out that I’m not the only one affected by this problem. And before trying out the various suggested solutions using `iptables` scripts, I thought I’d like to ask here before. I’m curious if there’s a clean fix for this under Rocky Linux 8.

Thanks & cheers from the rainy South of France.

---

<div class="post-metadata">

**Author:** ![iwalker](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/iwalker/32/2599_2.png) [@iwalker](https://forums.rockylinux.org/u/iwalker)\
**Post date:** [November 9, 2023, 7:11am UTC](https://forums.rockylinux.org/t/docker-ce-breaks-kvm-bridged-networking/11806/2 "2023-11-09T07:11:59Z")

</div>

Quickest and easiest - run Docker in a VM on the machine instead of attempting it to run alongside KVM. Or, instead of docker, use podman (unless that breaks KVM too) as this is available by default and practically the same (if not better in my opinion) than docker.

---

<div class="post-metadata">

**Author:** ![microlinux](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/microlinux/32/1244_2.png) [@microlinux](https://forums.rockylinux.org/u/microlinux)\
**Post date:** [November 9, 2023, 7:33am UTC](https://forums.rockylinux.org/t/docker-ce-breaks-kvm-bridged-networking/11806/3 "2023-11-09T07:33:10Z")

</div>

This sounds like a good solution. There’s only one problem with it. I’m teaching a course about Docker at the local university, and I need the real thing (e. g. Docker CE) on my workstation.

If it was only for my own purposes, I’d gladly run Podman.

---

<div class="post-metadata">

**Author:** ![iwalker](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/iwalker/32/2599_2.png) [@iwalker](https://forums.rockylinux.org/u/iwalker)\
**Post date:** [November 9, 2023, 7:44am UTC](https://forums.rockylinux.org/t/docker-ce-breaks-kvm-bridged-networking/11806/4 "2023-11-09T07:44:01Z")

</div>

Yep, totally understand. The VM route is probably the easiest than trying to get docker to play nicely with KVM.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex020/uploads/rockylinux/original/1X/91b7219eec10e30013422e4df76c1d898711a5d5.svg) [@system](https://forums.rockylinux.org/u/system)\
**Post date:** [January 8, 2024, 7:45am UTC](https://forums.rockylinux.org/t/docker-ce-breaks-kvm-bridged-networking/11806/5 "2024-01-08T07:45:01Z")

</div>

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.