All servers stop and don't come back on Ubuntu 24.04 (Proxmox VM)

Open
#211 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
40/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
docker, docker-compose, typescript, ubuntu

Research direction

Reproduce on a clean Ubuntu 24.04 VM using the standard isopod-compose.yml. Check the Isopod container's restart count and logs, the inner Docker daemon log, and docker inspect for server exit codes and OOMKilled status. Identify what stops the containers and fix that cause; if Isopod restarts, the issue points to the diagnostics issue and host-Docker mode for longer-term fixes.

Written by the indexing model from the issue text.

Description

bug

A self-hoster on Ubuntu 24.04.4 Server (full Proxmox VM, 16 cores, 10 GB RAM, SSD, Docker installed the usual way) reports that every server shuts down and never comes back. The server log shows the RCON client shutting down, which is what itzg prints when the container gets a stop signal, so something is stopping the containers rather than Minecraft crashing on its own. Raising each server from 1G to 4G changed nothing.

Since it hits every server at once, the main suspects are:

  • the Isopod container restarting, which takes its inner Docker daemon and all servers down with it;
  • the inner daemon losing access to cgroups or networking on this host (see docs/adr/0001-unprivileged-docker-in-docker.md), so containers stop or fail to start again;
  • the crash watchdog or restart policy treating a normal stop as a crash, or the other way round.

To do

  • Reproduce on a clean Ubuntu 24.04 VM with the standard isopod-compose.yml.
  • Check the Isopod container's restart count and logs, the inner daemon's log, and docker inspect of the server containers (exit code, OOMKilled, what sent the stop).
  • Fix the cause. If servers stop because Isopod restarts, the diagnostics issue and host-Docker mode cover the longer-term fixes.
Dominant language
TypeScript
Stars
1
Forks
0
Avg merge
13h 12m
Merged PRs (30d)
57

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Isopod-Project/Isopod

All issues in Isopod-Project/Isopod

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.