dockdiver

List all repositories in a Docker registry

$ dockdiver -url [https://example.com] -list

$ dockdiver -url [https://example.com] -dump [repository_name]

$ dockdiver -url [https://example.com] -dump-all -username [username] -password [password]

$ dockdiver -url [https://example.com] -dump [repository_name] -port [port] -rate [requests_per_second] -dir [path/to/output_directory]

$ dockdiver -url [https://example.com] -dump-all -bearer [bearer_token]

$ dockdiver -url [https://example.com] -list -headers ['{"X-Custom": "Value"}']

dockdiver [OPTIONS] <CONTAINER_NAME_OR_ID | IMAGE_NAME>

-i, --interactive
    Connects to an interactive shell (e.g., bash, sh) inside the specified container.

-f, --filesystem-view
    Provides an interactive view or browser for the container's filesystem, allowing easy navigation and inspection of files and directories.

-c, --command <CMD>
    Executes a single command <CMD> inside the container and then exits.

-p, --processes
    Lists processes currently running within the target container.

-e, --env
    Displays environment variables set inside the specified container.

-l, --layers
    When targeting an image, shows detailed information about its underlying layers and their contents.

-v, --version
    Displays the version information of the dockdiver utility.

-h, --help
    Shows a help message with available options and usage examples.

dockdiver is a powerful, hypothetical utility designed to provide a deep, interactive exploration of running Docker containers or container images. It allows users to "dive" into the container's environment, inspect its filesystem, view running processes, and even execute temporary commands within its isolated context, often streamlining tasks that would otherwise require repetitive use of standard docker exec commands. This tool is particularly useful for debugging, security analysis, and understanding container behavior by offering a unified and efficient way to navigate and analyze container internals directly from the host system. Its design prioritizes ease of use and quick insights, making it an essential, imagined utility for developers and system administrators working extensively with containerized applications.

As a hypothetical command, its actual caveats would depend on implementation. However, if it existed, dockdiver would likely require the Docker daemon to be running and accessible. It would also demand appropriate permissions to interact with the Docker socket, potentially requiring root or docker group membership. Furthermore, it might experience limitations with containers that do not have a standard shell (like bash or sh) installed when attempting interactive mode. Finally, it could pose potential security risks if used carelessly or by unauthorized users, as it grants deep access to container internals.

When invoked with the -i or --interactive option, dockdiver attempts to open a shell session (e.g., bash, sh) inside the specified container. This provides a familiar command-line environment for detailed investigation without directly attaching to the container's primary process, allowing for flexible debugging.

The -f or --filesystem-view option provides a specialized interface to browse the container's filesystem. This makes it easy to inspect files, directories, and their permissions directly from the host system, which is particularly useful for debugging application paths, missing files, or incorrect configurations within the container's isolated environment.

dockdiver is a hypothetical command, therefore its history is entirely conceptual. It is envisioned as emerging from the need for more efficient and intuitive debugging tools within the Docker ecosystem. While docker exec provides basic command execution, developers often found themselves repeatedly typing commands to explore container states. dockdiver was thus conceptualized to provide a unified, streamlined interface for interactive exploration, filesystem browsing, and process analysis within containers, reducing the friction of traditional exec workflows. Its imagined development would have focused on user experience and providing quick, deep insights into complex container environments.

docker(1), docker-exec(1), docker-inspect(1), nsenter(1)