Container Domain Access

Licobox assigns local domains to running containers, so you can open services without tracking host ports. A container named web is available at web.licobox.local, and Docker Compose services use the service.project.licobox.local format.

For web services, you can usually open the domain directly in your browser or call it from another local tool. This keeps projects with multiple services easier to navigate than a list of localhost ports.

Note

Container domains rely on Container Access via IP. Install licobox-helper first so Licobox can route traffic to container IP addresses.

Compose Projects

For Docker Compose, Licobox includes both the service name and the Compose project name in the domain:

service.project.licobox.local

The project name is usually based on the directory that contains your Compose file, unless you override it with Docker Compose options.

For example, a project named shop with api and postgres services can be reached at:

• api.shop.licobox.local
• postgres.shop.licobox.local

Ports

When a container exposes a web service, Licobox can route the domain to the detected HTTP service without requiring a port in the URL.

http://web.licobox.local

Ports are still useful for non-HTTP services or when you need to target a specific listener. For example, a Postgres service in the shop Compose project can still be addressed with its database port:

postgres.shop.licobox.local:5432

If a container runs more than one service, use the port explicitly when you want to avoid ambiguity.

How It Works

Domain access works through the same network path used for direct container IP access. If web.licobox.local does not resolve or connect, first confirm that Container Access via IP is working for the same container.