Docker containers can not start if there are no local interfaces up

If there are no local interfaces (Ethernet or WLAN) in above State, then the Docker bridge can not move to the above State too.
So containers are created but can not be started until the interface returns to above state.

It is a requirement that the target system can start and start services without being connected, so I wonder if it is an obvious behavior for the Docker daemon.

Is there any work around?
All containers are executed in the custom bridge.

I tried adding a virtual interface from veth and it seems that it helped, I will try to add one at the beginning as a temporary solution.