I'm running Debian 12.5 on a Dell Optiplex 990 with UEFI and a fast NVMe
drive with 16Gb RAM.  I've installed the latest Docker version 25.  I have
the exact same installation on a basic SATA spinning disk on the same
machine as well.

By default, Docker uses the Bridge network when running containers.  I'm
trying to build a Jekyll site using Docker, which fetches many Gem files
from rubygems.org.  My "docker run" command runs successfully for a
short period of time, but then can no longer make network connections out.
Also, my entire desktop's network capabilities are halted (i.e. browser,
apt, etc.).  When the container dies eventually, all network is restored on
the machine.  This is on my NVMe drive.  If I specify the "--network host"
option, it succeeds.

With the SATA drive installation, this all succeeds as expected.  The only
difference between the two installations is that the 8021q module (VLAN) is
loaded by default in my NVMe install that might be getting in the way but I
can't disable it.

I tested this with the latest Ubuntu and it works fine on that same NVMe
disk.

Any thoughts on this?  I use Docker very regularly.
Thank you, community!

Reply via email to