mirror of
https://github.com/open-webui/terminals.git
synced 2026-11-05 01:37:21 +00:00
[GH-ISSUE #54] FR: TERMINALS_NETWORK tiering support, and host network support #27
Labels
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
open-webui/terminals#27
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @i0ntempest on GitHub (Aug 31, 2026).
Original GitHub issue: https://github.com/open-webui/terminals/issues/54
It would be great if I can assign certain users' terminals to a particular docker network, so that I can assign who gets external network access. An example:
Admin/trusted users: terminal containers connect to priviledged bridge with internet and physical network access; or connect to a host network directly without a bridge
Normal users: on a bridge with internet access only (additional firewall rules), no local physical network access
Restricted users: on a pure internal bridge, no external net access
@owui-terminator[bot] commented on GitHub (Aug 31, 2026):
🔍 Related Issues Found
I found some existing issues that might be related. Please check if any of these are duplicates or contain helpful solutions:
🟣 #25 How to specify custom network?
This is directly about choosing a custom Docker network for spawned terminal containers, which is the core of the new request for assigning terminals to different networks.
by arp-mbender
🟣 #49 Single bridge network caps concurrent terminals at ~1024 (exchange full) — no sharding, no early warning
This issue discusses the current single
TERMINALS_NETWORKbridge design and explicitly proposes sharding across multiple networks, which overlaps with the requested tiered network support.by Classic298
🟣 #18 Container names exceed 63-character DNS label limit, breaking proxy routing
While not about tiering, it is related to Docker network/proxy behavior for spawned terminal containers on user-defined networks and may surface when changing network setup.
by dMwJr
💡 If your issue is a duplicate, please close it and add any additional details to the existing issue instead.
This comment was generated automatically. React with 👍 if helpful, 👎 if not.