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

Abierto
#24 2 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

  • #37 de @warhammered — cerrado sin fusionar

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
docker, linux, typescript

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.
Lenguaje dominante
TypeScript
Estrellas
277
Forks
27
Merge medio
2 h 47 min
PR fusionados (30 d)
1

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de DuskBotAI/duskbot

Todos los issues de DuskBotAI/duskbot

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.