[BUG] Stack cannot start with two networks

[lugaetsch]

Description

After updating to 1.0.20 I faced the following issue:
Bringing up a stack after defining gives an error in GUI and log (see above).
This seems to happen because one of the networks is marked as internal=true.

Using docker-compose up -d on the host itself works fine.

Steps to reproduce

1. Define stack
2. service has bridge-network and another bridge-network internal=true
3. Starting the stack causes error message

Logs

Container forgejo_db Creating 
 Container forgejo_db Created 
 Container forgejo Creating 
 Container forgejo Error response from daemon: Container cannot be connected to network endpoints: bridge_dev, bridge_proxy-internal 
Error response from daemon: Container cannot be connected to network endpoints: bridge_dev, bridge_proxy-internal

Browser logs

Dockhand version

1.0.20

Hawser version (if used)

No response

Connection mode

socket

Please confirm the following

• I have already searched for relevant existing issues and discussions before opening this report.
• I have updated the title field above with a concise description.