Licobox
New Local domains for every container

Docker containers for macOS.
Minimal setup.

Run Docker Engine on macOS. Licobox gives each container a local domain and lets you open its volumes in Finder.

brew install licobox/licobox-tap/licobox
Licobox desktop app showing running Docker containers

Works with your Docker workflow

3-4s Engine startup
0.2-0.5% Idle CPU on M3 Air
On demand Memory and disk usage
0 Port mappings needed

Features

Docker Engine, plus what Docker Desktop leaves out.

Your Docker CLI keeps working. Licobox adds local container domains and Finder access to volumes.

Docker Engine on macOS

Runs Docker Engine locally. Your existing Docker CLI and context work unchanged.

Learn more →

Local container domains

Every container gets a domain such as web.licobox.local, so you do not track host ports.

Learn more →

Direct access via IP

Reach a container by its IP address instead of mapping host ports.

Learn more →

Volumes in Finder

Mount a volume into macOS, then open, copy, or edit its files in Finder.

Learn more →

Debug distroless images

Attaches a shell with coreutils, htop, and curl to slim or distroless containers.

Learn more →

Low idle usage

Memory and disk grow and shrink with use. Idle CPU stays around 0.2% to 0.5% on an M3 MacBook Air.

Learn more →

Compare

Licobox vs Docker Desktop

Both run your Docker CLI. Licobox adds local domains and Finder volumes.

Feature Licobox Docker Desktop
Docker Engine on macOS ✓ ✓
Standard Docker CLI & context ✓ ✓
Container access via IP ✓ ✕
Local container domains ✓ ✕
Browse volumes in Finder ✓ ✕
Debug distroless containers ✓ ✕
Lightweight idle resource usage ✓ ✕

Rows reflect each product's default features. See the full feature list.

Up and running in seconds

Start Docker Engine on macOS, then run containers. Licobox forwards published ports for you.

  • Engine starts in 3 to 4 seconds
  • Access containers by IP or domain
  • Debug containers without changing the image
Get started →

Container access via domain

Every container gets a local domain such as web.licobox.local, so you can open a service without tracking host ports.

  • No host port mapping to remember
  • Works for standalone containers and Compose services
Learn more →

Debug any container

Inspect running containers without adding tools to the image. Licobox Debug attaches a shell with coreutils, htop, and curl, even for slim or distroless images.

  • Works on slim and distroless images
  • Install extra tools with pkgbox. They persist only in Licobox.
  • Files in /container stay untouched
Learn more →

Volume mounts on macOS

Mount Docker volumes into macOS and browse them in Finder.

  • Open, copy, and edit files in a volume
  • No shell needed to reach the files
Learn more →
Docker volume mounts browsed in macOS Finder

Install

Get started

Install Licobox, start the engine, and run a container. Add the Docker CLI if you do not have it.

terminal
$ brew install licobox/licobox-tap/licobox
$ licobox start
$ docker run -d -it -p 3000:3000 ghcr.io/licobox/getting-started:latest

Need the Docker CLI? Install it with brew install docker docker-compose docker-buildx. This installs the CLI only, not Docker Desktop. Read the install guide

FAQ

Common questions

What is Licobox?

Licobox runs Linux containers on macOS. It includes Docker Engine and a desktop app.

How do I install Licobox?

Install it with Homebrew: brew install licobox/licobox-tap/licobox.

Is Licobox free?

Yes. The core runtime is free for local development. Container access via IP, container debugging, and volume mounts to macOS are in the Pro plan.

How is it different from Docker Desktop?

Both run Docker Engine and Linux containers on macOS. Licobox adds container domains, IP access, port forwarding, container debugging, and volume mounts in Finder.

Run containers on macOS without Docker Desktop.

Install Licobox, then keep using the Docker CLI you know.