[GH-ISSUE #51] Request Feat: LXC containerisation #23

New issue

Open

opened 2026-10-18 21:13:30 +00:00 by bsakaguchi · 2 comments

bsakaguchi commented

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

Owner

Originally created by @mstarren on GitHub (Aug 2, 2026).
Original GitHub issue: https://github.com/open-webui/terminals/issues/51

Context

The use case for this repo is 1 person:1 env.

Problem

Dockers are not env-level containers, they are designed for application segmentation. They're very limited as a workspace.

Solution

LXC is designed for user/system segmentation. From the perspective of the user, it functions basically as if it's a VM; the only difference between LXC and a VM is that the point of LXC is to share the kernel runtime with host to preserve resources.

LXC is VM-like containerisation with docker-like resource consumption.

TL;DR:

Docker is not really the right tool for the job, LXC is.

Originally created by @mstarren on GitHub (Aug 2, 2026). Original GitHub issue: https://github.com/open-webui/terminals/issues/51 # Context The use case for this repo is 1 person:1 env. # Problem Dockers are not env-level containers, they are designed for application segmentation. They're very limited as a workspace. # Solution LXC is designed for user/system segmentation. From the perspective of the user, it functions basically as if it's a VM; the only difference between LXC and a VM is that the point of LXC is to share the kernel runtime with host to preserve resources. LXC is VM-like containerisation with docker-like resource consumption. # TL;DR: Docker is not really the right tool for the job, LXC is.

bsakaguchi commented

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

Author

Owner

@owui-terminator[bot] commented on GitHub (Aug 2, 2026):

⚠️ Invalid Issue Title

@mstarren, your issue title is too short, too few words, or a generic placeholder — it doesn't tell maintainers what's actually being reported or requested.

Please update the title to be at least 10 characters and 2 words, and to describe the actual issue. Bare placeholders like bug, feat:, or issue make triage difficult and slow down everyone.

Example: bug: Login fails when password contains special characters

@owui-terminator[bot] commented on GitHub (Aug 2, 2026): # ⚠️ Invalid Issue Title @mstarren, your issue title is too short, too few words, or a generic placeholder — it doesn't tell maintainers what's actually being reported or requested. Please update the title to be **at least 10 characters and 2 words**, and to describe the actual issue. Bare placeholders like `bug`, `feat:`, or `issue` make triage difficult and slow down everyone. Example: `bug: Login fails when password contains special characters`

bsakaguchi commented

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

Author

Owner

@owui-terminator[bot] commented on GitHub (Aug 2, 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:

🟣 #22 feat: propagate real resources into container
This issue is about making the container reflect the real CPU and memory limits instead of exposing host resources. It overlaps with the new request’s broader concern that Docker is not a good environment-level abstraction for a user workspace.
by Classic298
🟣 #23 feat: max storage does nothing on docker deployment
This is a Docker-deployment limitation around storage limits, which fits the same theme that Docker is too constrained for full environment/workspace isolation.
by Classic298
🟣 #39 issue: policy doesnt trigger for constantly running containers
This issue also discusses container lifecycle behavior for long-running user sessions, which is part of the broader container-as-workspace discussion in the new LXC feature request.
by Classic298

💡 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.

@owui-terminator[bot] commented on GitHub (Aug 2, 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: 1. 🟣 [#22](https://github.com/open-webui/terminals/issues/22) **feat: propagate real resources into container** *This issue is about making the container reflect the real CPU and memory limits instead of exposing host resources. It overlaps with the new request’s broader concern that Docker is not a good environment-level abstraction for a user workspace.* *by Classic298* 2. 🟣 [#23](https://github.com/open-webui/terminals/issues/23) **feat: max storage does nothing on docker deployment** *This is a Docker-deployment limitation around storage limits, which fits the same theme that Docker is too constrained for full environment/workspace isolation.* *by Classic298* 3. 🟣 [#39](https://github.com/open-webui/terminals/issues/39) **issue: policy doesnt trigger for constantly running containers** *This issue also discusses container lifecycle behavior for long-running user sessions, which is part of the broader container-as-workspace discussion in the new LXC feature request.* *by Classic298* --- 💡 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.

bsakaguchi referenced this issue

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

[PR #27] [MERGED] fix: best-effort max storage on docker backend #52