termux/proot-distro

A utility for managing proot containers.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 40 minutes ago
Added to GitGenius on September 19th, 2026
Created on July 20th, 2020
Open Issues & Pull Requests: 5 (+1)
GitHub issues: Enabled
Number of forks: 481
Total Stargazers: 3,493 (+0)
Total Subscribers: 59 (+0)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 4
New in 7 days: 2
Closed in 7 days: 2
Avg open age: 115 days
Stale 30+ days: 2
Stale 90+ days: 0

Recent activity

Opened in 7 days: 1
Closed in 7 days: 2
Comments in 7 days: 2
Events in 7 days: 4

Top labels

  • bug report (59)
  • question (49)
  • enhancement (48)
  • invalid (21)
  • proot-bug (9)
  • not-bug (4)
  • wontfix (4)
  • bug (2)

Detailed Description

PRoot-Distro is a utility for managing rootless Linux containers in Termux and on regular Linux hosts.

The tool solves the problem of running full Linux distributions on Android devices or non-root Linux environments without requiring root access, a kernel module, or a Docker daemon. It uses proot to provide a chroot-like environment and assembles container filesystems by pulling Docker and OCI images directly from registries like Docker Hub or extracting local tarballs. The tool can also build OCI images from Dockerfiles and push them to registries, all without needing a Docker daemon.

PRoot-Distro suits developers and users who want to run desktop-class Linux distributions on phones or tablets, cross-compile for different CPU architectures using QEMU user-mode, deploy server software like Nginx or PostgreSQL on Android using standard OCI images, or build and push custom images on-device. It is particularly valuable for non-destructive experimentation with distributions since containers can be easily removed after use. The tool exposes its CLI as both proot-distro and the shorter pd alias.

The project maintains active engagement with its user base through regular issue responses and pull request reviews. Development includes consistent refinement of core functionality and expansion of supported use cases. The codebase receives ongoing updates to handle edge cases and improve reliability across different environments and container types.