chroot-distro 2.2.0__tar.gz → 2.3.0__tar.gz

{chroot_distro-2.2.0 → chroot_distro-2.3.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: chroot-distro
-Version: 2.2.0
+Version: 2.3.0
 Summary: chroot-distro is a lightweight Linux container management utility built around chroot.
 Project-URL: Homepage, https://github.com/sabamdarif/chroot-distro
 Project-URL: Repository, https://github.com/sabamdarif/chroot-distro
@@ -78,6 +78,7 @@ when needed (see [First-run check](#first-run-check)).
    * [`copy`](#copy--copy-files-to-or-from-a-container)
    * [`sync`](#sync--synchronize-files-to-or-from-a-container)
    * [`clear-cache`](#clear-cache--delete-the-download-cache)
+   * [`info`](#info--show-host-and-container-diagnostics)
    * [`help`](#help--show-command-help)
 3. [How Chroot-Distro works](#how-chroot-distro-works)
 4. [Storage layout](#storage-layout)
@@ -166,8 +167,9 @@ order: `sudo`, `doas`, `pkexec`, or `su`.
 | Termux, default | Prefer `su` (real root) over `sudo`. |
 | Termux, `--use-sudo` or `CHROOT_DISTRO_USE_SUDO=1` | Prefer `sudo` for elevation. |
 
-`list`, `ps`, `search`, and `help` do not require root and are never
-re-executed.
+`list`, `ps`, `search`, `info`, and `help` do not require root on Termux and
+are never re-executed. On regular Linux, `list`, `ps`, and `info` still
+elevate to inspect root-owned data.
 
 ### Quick start
 
@@ -203,6 +205,9 @@ chroot-distro ps
 # Search Docker Hub for an image
 chroot-distro search nextcloud
 
+# Print diagnostic report for host and containers
+chroot-distro info
+
 # See what changed in a container relative to its image
 chroot-distro diff ubuntu
 
@@ -1031,6 +1036,27 @@ network access again.
 
 ---
 
+### `info` — Show host and container diagnostics
+
+```
+chroot-distro info
+Aliases: version-info, nf
+```
+
+Print a structured diagnostics report about the host and installed containers. Useful to attach when filing a bug report so issues can be reproduced and triaged faster.
+
+The report covers five sections:
+
+- **Program** — `chroot-distro` version, Python version, data location.
+- **Host** — On Termux: Termux version, Android release/SDK, device. On Linux: distribution name/version, kernel, libc. Host CPU architecture and 32-bit support are shown in both cases.
+- **Capabilities** — Host checks that affect launching containers: privilege-escalation tool (`sudo`/`doas`/`pkexec`/`su`), Termux `/data` suid/exec flags, `binfmt_misc` + QEMU for foreign architectures, `unshare`/`nsenter` and user-namespace support, free disk space on the data dir, download cache size, and SELinux/AppArmor mode.
+- **Images** — Every installed container with rootfs size, detected architecture, image source, busy/idle status, plus source URL and image type from manifest labels when available.
+- **Analysis** — Lightweight checks per image: architecture mismatch against the host, missing manifest, empty or unusual rootfs.
+
+Like `list` and `ps`, `info` is a read-only command that does not require root on Termux. On regular Linux hosts, it automatically elevates to inspect the same root-owned data directory where containers are installed.
+
+---
+
 ### `help` — Show command help
 
 ```

{chroot_distro-2.2.0 → chroot_distro-2.3.0}/README.md

@@ -49,6 +49,7 @@ when needed (see [First-run check](#first-run-check)).
    * [`copy`](#copy--copy-files-to-or-from-a-container)
    * [`sync`](#sync--synchronize-files-to-or-from-a-container)
    * [`clear-cache`](#clear-cache--delete-the-download-cache)
+   * [`info`](#info--show-host-and-container-diagnostics)
    * [`help`](#help--show-command-help)
 3. [How Chroot-Distro works](#how-chroot-distro-works)
 4. [Storage layout](#storage-layout)
@@ -137,8 +138,9 @@ order: `sudo`, `doas`, `pkexec`, or `su`.
 | Termux, default | Prefer `su` (real root) over `sudo`. |
 | Termux, `--use-sudo` or `CHROOT_DISTRO_USE_SUDO=1` | Prefer `sudo` for elevation. |
 
-`list`, `ps`, `search`, and `help` do not require root and are never
-re-executed.
+`list`, `ps`, `search`, `info`, and `help` do not require root on Termux and
+are never re-executed. On regular Linux, `list`, `ps`, and `info` still
+elevate to inspect root-owned data.
 
 ### Quick start
 
@@ -174,6 +176,9 @@ chroot-distro ps
 # Search Docker Hub for an image
 chroot-distro search nextcloud
 
+# Print diagnostic report for host and containers
+chroot-distro info
+
 # See what changed in a container relative to its image
 chroot-distro diff ubuntu
 
@@ -1002,6 +1007,27 @@ network access again.
 
 ---
 
+### `info` — Show host and container diagnostics
+
+```
+chroot-distro info
+Aliases: version-info, nf
+```
+
+Print a structured diagnostics report about the host and installed containers. Useful to attach when filing a bug report so issues can be reproduced and triaged faster.
+
+The report covers five sections:
+
+- **Program** — `chroot-distro` version, Python version, data location.
+- **Host** — On Termux: Termux version, Android release/SDK, device. On Linux: distribution name/version, kernel, libc. Host CPU architecture and 32-bit support are shown in both cases.
+- **Capabilities** — Host checks that affect launching containers: privilege-escalation tool (`sudo`/`doas`/`pkexec`/`su`), Termux `/data` suid/exec flags, `binfmt_misc` + QEMU for foreign architectures, `unshare`/`nsenter` and user-namespace support, free disk space on the data dir, download cache size, and SELinux/AppArmor mode.
+- **Images** — Every installed container with rootfs size, detected architecture, image source, busy/idle status, plus source URL and image type from manifest labels when available.
+- **Analysis** — Lightweight checks per image: architecture mismatch against the host, missing manifest, empty or unusual rootfs.
+
+Like `list` and `ps`, `info` is a read-only command that does not require root on Termux. On regular Linux hosts, it automatically elevates to inspect the same root-owned data directory where containers are installed.
+
+---
+
 ### `help` — Show command help
 
 ```

{chroot_distro-2.2.0 → chroot_distro-2.3.0}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "chroot-distro"
-version = "2.2.0"
+version = "2.3.0"
 description = "chroot-distro is a lightweight Linux container management utility built around chroot."
 readme = "README.md"
 requires-python = ">=3.10"

{chroot_distro-2.2.0 → chroot_distro-2.3.0}/src/chroot_distro/cli.py

@@ -10,6 +10,7 @@ from chroot_distro.commands.clear_cache import command_clear_cache
 from chroot_distro.commands.copy import command_copy
 from chroot_distro.commands.diff import command_diff
 from chroot_distro.commands.help import HELP_COMMANDS, command_help
+from chroot_distro.commands.info import command_info
 from chroot_distro.commands.install import command_install
 from chroot_distro.commands.kill import command_kill
 from chroot_distro.commands.list_cmd import command_list
@@ -59,6 +60,7 @@ _COMMAND_HANDLERS = {
     "ps": command_ps,
     "diff": command_diff,
     "search": command_search,
+    "info": command_info,
     "help": command_help,
 }
 
@@ -186,13 +188,15 @@ def main() -> None:
     # Root check requirement:
     # - In normal Linux: all commands require root except "help"
     # - In Termux: all commands require root except "list" and "help"
-    # `search` is network-only and never needs root. `ps` and `list` only read
-    # /proc and container metadata, so they are exempt on Termux like `help`.
+    # `search` is network-only and never needs root. `ps`, `list`, and `info`
+    # only read /proc and container metadata, so they are exempt on Termux like
+    # `help`. On Linux containers are installed by root and live in root's data
+    # dir, so these commands still elevate there to read the right location.
     requires_root = False
     if canonical in ("help", "search"):
         requires_root = False
     elif IS_TERMUX:
-        if canonical not in ("list", "ps"):
+        if canonical not in ("list", "ps", "info"):
             requires_root = True
     else:
         requires_root = True

{chroot_distro-2.2.0 → chroot_distro-2.3.0}/src/chroot_distro/commands/help/pages.py

@@ -640,6 +640,42 @@ HELP_PAGES: dict[str, dict[str, typing.Any]] = {
             f"{PROGRAM_NAME} search --limit 50 ubuntu",
         ],
     },
+    "info": {
+        "usage": "info",
+        "aliases": ("version-info", "nf"),
+        "summary": (
+            "Print a structured diagnostics report about the host and installed "
+            "containers. Useful to attach when filing a bug report so issues can "
+            "be reproduced and triaged faster."
+            "\n\n"
+            "The report covers five sections:"
+            "\n\n"
+            "  Program  chroot-distro version, Python version, data location.\n"
+            "  Host     On Termux: Termux version, Android release/SDK, device. "
+            "On Linux: distribution name/version, kernel, libc. Host CPU "
+            "architecture and 32-bit support are shown in both cases.\n"
+            "  Capabilities Host checks that affect launching containers: "
+            "privilege-escalation tool (sudo/doas/pkexec/su), Termux /data "
+            "suid/exec flags, binfmt_misc + QEMU for foreign architectures, "
+            "unshare/nsenter and user-namespace support, free disk space on "
+            "the data dir, download cache size, and SELinux/AppArmor mode.\n"
+            "  Images   Every installed container with rootfs size, detected "
+            "architecture, image source, busy/idle status, plus source URL and "
+            "image type from manifest labels when available.\n"
+            "  Analysis Lightweight checks per image: architecture mismatch "
+            "against the host, missing manifest, empty or unusual rootfs."
+            "\n\n"
+            "Read-only. Like 'list' it is rootless on Termux, but elevates on "
+            "regular Linux to read the root-owned data directory where "
+            "containers are installed."
+        ),
+        "options": [
+            ("-h, --help", "Show this help."),
+        ],
+        "examples": [
+            f"{PROGRAM_NAME} info",
+        ],
+    },
     "sync": {
         "usage": "sync [OPTIONS] [DIST:]SRC [DIST:]DEST",
         "summary": (
@@ -697,4 +733,5 @@ TOP_COMMANDS = [
     ("kill", "Forcibly stop a running container."),
     ("diff", "Inspect filesystem changes in a container."),
     ("search", "Search Docker Hub for images."),
+    ("info", "Show host and container diagnostics for bug reports."),
 ]