Containers unreachable after upgrade from 3.0 to 4.0

Describe the bug

Hi,

I newly upgraded my Photon 3.0 to 4.0 today. Upgrade was successful and it can boot properly.
I can access to the Photon OS via SSH, so I can confirm that the OS and it's IP Address is ok.
It's that all the containers are now unreachable on the network. I can see the containers up and running with the IP assigned, but I suspect the containers are somehow not connected to the network.

I connect to one of the container's shell and tried pinging to other host but it's unreachable. Then I check networkctl and the result as per below. Thanks in advance.

[ ~ ]$ networkctl
IDX LINK TYPE OPERATIONAL SETUP
1 lo loopback carrier unmanaged
2 eth0 ether routable configured
3 br-5f993280fc82 bridge no-carrier unmanaged
4 br-61d7fa096103 bridge no-carrier unmanaged
5 br-8cf937f16283 bridge no-carrier unmanaged
6 br-e5ca7561b3a6 bridge no-carrier unmanaged
7 br-07cc005c9835 bridge no-carrier unmanaged
8 br-5241b1e0f073 bridge no-carrier unmanaged
9 br-ee224c333cc6 bridge no-carrier unmanaged
10 br-b282f9dbe180 bridge no-carrier unmanaged
11 docker0 bridge routable unmanaged
15 vethfaa779a ether degraded unmanaged
17 vethbb25be9 ether degraded unmanaged
19 veth1db171a ether degraded unmanaged
21 veth09a9a42 ether degraded unmanaged

Reproduction steps

1. Upgrade Photon OS from 3.0 to 4.0
2. Restart the OS after upgrade
3. Check running container for network connection
   ...

Expected behavior

All containers are reachable on the network after upgrade

Additional context

No response

No repository file or test is identified. Reproduce the Photon OS 3.0-to-4.0 upgrade, inspect the container bridge and veth state shown by networkctl, and compare networking before and after the restart; done means running containers are reachable on the network after the upgrade.