[GH-ISSUE #25] How to specify custom network? #8

New issue

Closed

opened 2026-10-18 21:13:20 +00:00 by bsakaguchi · 1 comment

bsakaguchi commented

2026-10-18 21:13:20 +00:00

Owner

Originally created by @arp-mbender on GitHub (May 22, 2026).
Original GitHub issue: https://github.com/open-webui/terminals/issues/25

My docker-compose setup has the LLM stack working in a specific, predefined docker network, which now includes terminals. However terminals is seemingly unaware of this, and will create a new docker instance in the default network.

Is there a way to let terminals know which network it's supposed to use when spinning up new containers?

Originally created by @arp-mbender on GitHub (May 22, 2026). Original GitHub issue: https://github.com/open-webui/terminals/issues/25 My docker-compose setup has the LLM stack working in a specific, predefined docker network, which now includes `terminals`. However `terminals` is seemingly unaware of this, and will create a new docker instance in the default network. Is there a way to let `terminals` know which network it's supposed to use when spinning up new containers?

bsakaguchi closed this issue

2026-10-18 21:13:20 +00:00

bsakaguchi commented

2026-10-18 21:13:20 +00:00

Author

Owner

@james-westbrook commented on GitHub (May 24, 2026):

Hi @arp-mbender, you can use the TERMINALS_NETWORK environment variable to set a predefined Docker network for terminals containers to end up in.

@james-westbrook commented on GitHub (May 24, 2026): Hi @arp-mbender, you can use the `TERMINALS_NETWORK` environment variable to set a predefined Docker network for terminals containers to end up in.

bsakaguchi referenced this issue

2026-10-18 21:13:44 +00:00

[PR #8] [CLOSED] FIX #7 #43