When you configure a bridged network connection, you’re not creating a bridged connection between Guest and HostOS, you’re creating that connection between the Guest and a specified HostOS network interface. In other words, your Guest network connection isn’t communicating exclusively with the HostOS, it’s communicating with every machine, physical or otherwise on that network and is seen as though it’s another physical machine.
When you configure any kind of network connection in the Guest Settings, VBox presents an environment to the Guest… The Guest doesn’t know better and no matter what kind of network connection is configured, the Guest will always think it’s a regular wired connection. Typically in any Guest the only major configuration you should make is whether it’s a DHCP client or not, and if the latter then you’ll need to configure static network addressing, and how you configure in the Guest is no different than configuring a physical machine on the network.
Bottom line is that your Guest should ordinarily never see a “bridged connection” or a “NAT connection” or whatever else might be configured in VBox… To the Guest, it’s a regular wired connection, always. If you do so for a special reason, that’s an advanced topic most people should never need to know about.
So, your specific questions
- Should the VirtualBox virtual network adapter be listed on the host machine
Virtual networks are configured in the Virtual Manager running on the HostOS.
virtual network adapters are listed in the Guest Settings (Networking).
And, as I described you should never see a virtual network adapter inside a Guest, within the Guest everything looks “real.”
- Any special considerations in setting bridged networking between VBox and Thumbeweed
Nothing special.
As described, you first select the type of network connection in the Guest Settings.
Then, because the Guest can’t tell the diff between real or virtual, you configure the Guest using ordinary methods depending on the network it’s connecting to, and whether various networking services are provided… like always.
As for your Docker network connections… That depends entirely on what kind of network connection you specify. By default, a container shouldn’t have any network connectivity, you have to pass to the container a network configuration when you execute your “run” command.
If you’re looking for more information related to virtualization, don’t forget to search the Virtualization Forum, you’ll find more information there than here in the Networking forum.
TSU