Docker Compose
Detection
The compose file is located by walking up from the current directory. Filenames, in priority
order within a directory: docker-compose.yml, compose.yaml, compose.yml.
The search climbs at most 3 parent directories; a nearer directory always
wins over a farther one.
Only common ports: forms are supported ("3000", "8080:80", "127.0.0.1:8080:80", optional /tcp|/udp, and the long {target, published} form) — not
the full Compose specification.
rundock services
Lists every service, its published ports, and whether it is safe to expose. A service is
marked private when its name looks like a datastore (postgres, redis, mysql, mongo) or it publishes no host port.
$ Exposing one service
rundock expose <service> [--port N] [--yes] opens a public tunnel to a single compose service, resolving its published port automatically. Flags
may precede or follow the service name.
- --port N
- Required when a service publishes more than one port.
- --yes
- Skip the confirmation prompt for a private/risky service.
A private service prompts before exposing:
$ Stack mode
Expose every service at once: one tunnel per exposable service, opened concurrently. Private services are skipped with a note.
$ Limitations
- A service literally named "stack" cannot be exposed by name (expose stack always means "expose all"); rename it to expose it individually.
- In stack mode a multi-port service uses its first published mapping.
- Space-separated inline passwords are not supported for tunnel; use --password (prompt) or --password=SECRET.
See the full CLI reference for every command and flag.