Open
Description
Describe the bug
Ports exposed by docker externally do not work after the VM is resumed. I've tracked this to the /etc/vmware-tools/scripts/vmware/network
script. It should ignore docker interfaces.
Here are part of the vmware-network.log showing the interfaces the script is managing.
Sat Dec 14 12:43:24 PM UTC 2024 : [rescue_nic] ens160 is already active.
Sat Dec 14 12:43:24 PM UTC 2024 : [rescue_nic] activating br-0d1a7715135b ...
Sat Dec 14 12:43:24 PM UTC 2024 : [rescue_nic] activating br-809bc452502f ...
Sat Dec 14 12:43:24 PM UTC 2024 : [rescue_nic] activating docker0 ...
Sat Dec 14 12:43:24 PM UTC 2024 : [rescue_nic] activating vethae88d5b ...
Sat Dec 14 12:43:24 PM UTC 2024 : [rescue_nic] activating veth4d6888e ...
Sat Dec 14 12:43:24 PM UTC 2024 : [rescue_nic] activating vethf0ca46a ...
Sat Dec 14 12:43:24 PM UTC 2024 : [rescue_nic] activating veth48cd19e ...
Sat Dec 14 12:43:24 PM UTC 2024 : [rescue_nic] activating vethc6f3655 ...
Sat Dec 14 12:43:24 PM UTC 2024 : [rescue_nic] activating veth114e267 ...
Sat Dec 14 12:43:24 PM UTC 2024 : [rescue_nic] activating veth510625f ...
Sat Dec 14 12:43:24 PM UTC 2024 : [rescue_nic] activating veth167d3f2 ...
Sat Dec 14 12:43:24 PM UTC 2024 : [rescue_nic] activating vethac2c5ba ...
Sat Dec 14 12:43:24 PM UTC 2024 : [rescue_nic] activating veth6115ac2 ...
Sat Dec 14 12:43:24 PM UTC 2024 : [rescue_nic] activating veth4f5c84c ...
Sat Dec 14 12:43:24 PM UTC 2024 : [rescue_nic] activating veth07f7c58 ...
Sat Dec 14 12:43:24 PM UTC 2024 : [rescue_nic] activating br_kasm_sidecar ...
Sat Dec 14 12:43:24 PM UTC 2024 : [rescue_nic] activating k-p-e-2af88f ...
Reproduction steps
- Install docker
- Run an app that exposes ports, such as https://kasmweb.com/
- suspend/resume
- nc -nzv 198.168.1.183 443 (replace with IP address of VM)
Expected behavior
Exposed ports should be accessible after resume.
Additional context
No response