Docker provider

The Docker provider mounts your Docker daemon into /docker, exposing containers, system metadata, and Compose projects as regular files. No SDK, no API client: ls lists running containers, cat reads state.

Mount point

All paths are under /omnifs/docker/ once the provider is loaded. The examples below use /omnifs as the mount root; adjust if you configured a different mount point.

Configuration

One optional config key:

Key	Type	Required	Default
endpoint	string	no	unix:///var/run/docker.sock

Set endpoint only when connecting to a remote daemon or a non-standard socket path. The default works for Docker Desktop and most Linux installs.

Note

The provider connects through the endpoint you configure. It never opens additional sockets or escalates privileges. The host holds the connection; the WASM component receives only the data it explicitly requests.

System info

Two files describe the daemon itself:

/docker/system/info.json
/docker/system/version.json

cat /omnifs/docker/system/version.json

Both files are read-only snapshots returned on demand. They reflect the daemon’s current state at the time of the read.

Containers

List running and stopped containers

ls /omnifs/docker/containers/_running
ls /omnifs/docker/containers/_stopped

Example output:

nginx  postgres  redis

Each entry is a container name. The _running and _stopped directories are virtual; omnifs populates them live from the daemon.

Inspect a container by name

Three files are available under containers/by-name/{name}/:

File	Contents
state	Current lifecycle state (running, exited, paused, etc.)
inspect.json	Full docker inspect output as JSON
summary.txt	Human-readable summary: image, status, ports, mounts

cat /omnifs/docker/containers/by-name/postgres/state

running

cat /omnifs/docker/containers/by-name/postgres/inspect.json

cat /omnifs/docker/containers/by-name/postgres/summary.txt

Inspect a container by ID

The same three files are available under containers/by-id/{id}/:

cat /omnifs/docker/containers/by-id/a3f9c12b8e01/state
cat /omnifs/docker/containers/by-id/a3f9c12b8e01/inspect.json

You can use a prefix of the container ID as long as it is unambiguous.

Compose projects

Containers belonging to a Compose project are reachable under a structured path:

/docker/compose/{project}/services/{service}/containers/{name}

ls /omnifs/docker/compose/myapp/services/web/containers/

This is a directory listing: each entry is a container name running that service. From there, use by-name or by-id paths to read state and inspect data.

Note

The Compose subtree reflects what the daemon knows. If containers were started outside Compose, they do not appear here, but they remain reachable under containers/by-name/ and containers/by-id/.

Quick reference

Path	Op	What you get
/docker/system/info.json	cat	Daemon info
/docker/system/version.json	cat	API and engine versions
/docker/containers/_running	ls	Names of running containers
/docker/containers/_stopped	ls	Names of stopped containers
/docker/containers/by-name/{name}/state	cat	Lifecycle state string
/docker/containers/by-name/{name}/inspect.json	cat	Full inspect payload
/docker/containers/by-name/{name}/summary.txt	cat	Human-readable summary
/docker/containers/by-id/{id}/inspect.json	cat	Full inspect payload by ID
/docker/compose/{project}/services/{service}/containers/{name}	ls	Containers for a Compose service

Common patterns

Find which containers are currently stopped:

ls /omnifs/docker/containers/_stopped

Check the state of every running container in one pass:

for c in /omnifs/docker/containers/_running/*; do
  printf "%s: %s\n" "$(basename "$c")" "$(cat /omnifs/docker/containers/by-name/"$(basename "$c")"/state)"
done

Grep an inspect payload without docker inspect:

grep -i "IPAddress" /omnifs/docker/containers/by-name/nginx/inspect.json

Pull exposed ports for all running containers:

grep -h "Ports" /omnifs/docker/containers/by-name/*/summary.txt