Run server containers on the host's Docker instead of Docker-in-Docker

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

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
docker, typescript

Research direction

Start with docs/adr/0001-unprivileged-docker-in-docker.md and trace how Isopod currently creates server containers and handles bind-mount paths. The issue does not name implementation files or tests, so locate those entry points before changing behavior. Done means host-Docker installs can discover labeled server containers after restart, publish any free port, and leave servers running when Isopod stops; preserve Docker-in-Docker for CasaOS and document migration and socket access risks.

Written by the indexing model from the issue text.

Description

enhancement

Isopod creates the server containers inside its own Docker daemon (Docker-in-Docker, docs/adr/0001-unprivileged-docker-in-docker.md). That was done to keep servers off the CasaOS home screen, but it has real costs, which a self-hoster raised:

  • If the Isopod container stops, restarts, or is reinstalled, every server goes down with it.
  • Every port has to be published on the Isopod container ahead of time, which caps it at 21 Java and 21 Bedrock servers on fixed ranges.
  • Server logs and containers are hidden from the host's Docker tools.
  • The container needs SYS_ADMIN, NET_ADMIN, and unconfined seccomp and AppArmor.

Proposal

Add a mode where Isopod manages server containers on the host's Docker (sibling containers), and make it the default for plain Linux installs. Keep Docker-in-Docker for CasaOS.

  • Servers keep running when the dashboard is stopped, updated, or reinstalled, and Isopod picks them up again by label.
  • Ports are published per server container, so there's no fixed range.
  • Bind-mount paths have to match between the host and the Isopod container; handle that.
  • Migration path for existing installs (move containers and images out of the inner daemon).
  • The ADR notes that socket access is root-equivalent; update it to cover this mode.

Acceptance

  • On a host-Docker install, docker ps on the host lists the servers, and stopping Isopod leaves them running.
  • Servers can use any free port.
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.