FreeVisit Website
Tracked since2026
0 reviews trackedThe Bottom Line
Entry price
Free, no paid tier
Biggest pro
Lightweight and fast due to Rust implementation
Biggest con
Exec into container feature not available on Windows
TL;DR - Oxker
- Terminal User Interface (TUI) for Docker container management.
- Built in Rust for performance and efficiency.
- Offers viewing, controlling, and logging of Docker containers.
Pricing: Free forever
Best for: Individuals & startups
What is Oxker?
Oxker is a terminal user interface (TUI) application built in Rust, designed to provide an intuitive way to view and control Docker containers. It leverages `ratatui` for the TUI and `Bollard` for Docker interaction, offering a lightweight and efficient solution for managing your Docker environment directly from the command line.
This tool is ideal for developers, DevOps engineers, and anyone working with Docker containers who prefers a keyboard-driven interface over a graphical one or needs to manage containers in a remote or server environment. It simplifies common Docker operations like viewing logs, executing commands within containers, and sorting container lists.
Key benefits include increased productivity through a fast, responsive TUI, the ability to customize keymaps and color schemes for a personalized experience, and broad compatibility across various operating systems and Docker environments, including installation via Cargo, Docker, Nix, AUR, Homebrew, or pre-built binaries.
Available on: Linux, macOS
Pros & Cons
Pros
- Lightweight and fast due to Rust implementation
- Keyboard-driven interface for efficient workflow
- Highly customizable through configuration files
- Multiple installation methods (Cargo, Docker, Nix, Homebrew, pre-built binaries)
- Provides detailed container logs with filtering and saving options
Cons
- Exec into container feature not available on Windows
- Requires familiarity with terminal applications
- Limited functionality in 'no TUI' debugging mode
Preview
Key Features
View Docker containers in a TUIControl Docker containers (e.g., exec, stop)View container logs with optional coloring and timestamp removalFilter and sort containersSave container logs to fileCustomizable keymaps and color schemes via config fileExec into selected containers (not on Windows)Toggle help menu and mouse capture
Pricing Plans
Pricing checked May 29, 2026
Open Source
Free
- Full source code access
- MIT License license
- Community support
- Self-hosted
Reviews
Be the first to review Oxker
Your take helps the next buyer. Verified LinkedIn reviewers get a badge.
Write a reviewBest Oxker Alternatives
Top alternatives based on features, pricing, and user needs.
Still deciding?
Most buyers shortlist 2 or 3 tools before committing. Pull a side-by-side comparison or browse the full alternatives shortlist below.
Explore More
Oxker FAQ
How can I install oxker on a Linux system without using a package manager?
You can install oxker on Linux by downloading the pre-built binary. A one-liner command using
wget and tar is available to fetch the oxker_linux_x86_64.tar.gz file, extract it, and install the executable to your HOME/.local/bin directory.What methods are available for running oxker within a Docker environment?
oxker can be run as a Docker container using images published on ghcr.io or Docker Hub. You can execute a
docker run command, mounting the Docker socket to allow oxker to interact with your Docker daemon.Can I customize the keyboard shortcuts and color scheme in oxker?
Yes, oxker allows for customization of settings, including keymaps and color schemes, through a configuration file. Examples of this file, supporting
.toml, .json, and .jsonc formats, can be found in the example_config directory.How do I save logs from a container using oxker, and can I specify the output directory?
You can save logs from a selected container by pressing 's'. By default, logs are saved to
$HOME/[container_name]_[timestamp].log, but you can specify a custom directory using the --save-dir command-line argument.What command-line arguments are available to control the display of logs in oxker?
oxker offers several command-line arguments for log display:
-r shows raw logs, -c attempts to color logs (conflicts with -r), --no-stderr excludes stderr output, and -t removes timestamps from each log entry.Is it possible to connect oxker to a Docker daemon on a custom host or through an environment variable?
Yes, oxker can connect to Docker using a custom hostname specified by the
--host command-line argument, which defaults to /var/run/docker.sock. It will also utilize the $DOCKER_HOST environment variable if it is set.Source: github.com