Shared computer at its memory cap: docker exec times out, every bot shows "team computer is being changed", restart/kill hang under gVisor

未关闭
#24 2 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

  • #37 来自 @warhammered —— 已关闭,未合并

评估

难度
5/5
预计耗时
一周以上
新手友好度
35/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
docker, linux, typescript

调研方向

The report describes memory limits, browser allocation, container recovery, lifecycle locking, and restart behavior, but names no source files, tests, or entry points. Start by locating the shared computer lifecycle and container management code, then trace how browser requests and Docker restarts are handled. Done means the reported failure modes have defined fixes and regression coverage; the issue does not specify acceptance criteria.

由索引模型根据 Issue 内容生成。

描述

Version

0.2.15

Platform

Own server (Windows 11 + WSL2 Ubuntu 24.04, 15.8 GB RAM, WSL memory=10GB at the time)

What happened

On 17 Nov about 16:50 WIB the shared computer container (openmausbot-vps-computerf3d9-..., runtime runsc) reached 7.18 of its 7.2 GB limit with 355 processes, because every bot opened its own browser in it. Then:

  • docker exec timed out, mcp__agents__vm_exec calls failed after up to 338 s (94 calls, median 1.9 s, p90 60 s, 81% ok);
  • every bot in every group showed "The team computer is being changed" and stopped;
  • docker restart and docker kill both hung. Only kill -9 of the runsc-sandbox process plus docker start recovered it.

Earlier the same day (15:17 WIB) the in-memory remoteComputerLifecycleBusyOwners flag for the same computer was never released although the container was up, and mountTeamVps kept throwing until duskbot was restarted.

Suggested fix
  1. Watch the container's memory and refuse or queue a new browser screen when it is above about 85%, with a message saying why.
  2. Default bots that never use a browser to no team computer (we set computer:"off" on 10 of 20 bots by hand).
  3. When docker stop/kill does not return in 20 s on runsc, kill the sandbox process and restart the container automatically.
  4. Release the lifecycle busy flag in a finally, and expire it after a timeout.
  5. Keep a memory limit set with docker update when the container is restarted, instead of resetting it.
主要语言
TypeScript
星标
277
派生
27
平均合并
2 小时 47 分钟
30 天内合并 PR
1

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

DuskBotAI/duskbot 的其他 Issue

查看 DuskBotAI/duskbot 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。