Skip to content
Docker Engine

Container names

Licobox gives every running container a local name, so you can open a service without tracking host ports. A container named web answers at web.licobox.local.

Type a container or service name to see the local name Licobox gives it.

http://web.licobox.local

<container>.licobox.local

A container named web opens at:

http://web.licobox.local
  1. Start the container while Licobox is running.
  2. Open the name in your browser, or call it from another local tool.
  3. If the name does not resolve, confirm that Container IPs works for the same container.
Container or serviceTypeAddress
webSingle containerhttp://web.licobox.local
api in shopCompose servicehttp://api.shop.licobox.local
postgres in shopCompose servicepostgres.shop.licobox.local:5432

For Docker Compose, Licobox joins the service name and the project name with a dot. The project name comes from the directory that holds the Compose file, unless you override it with Docker Compose options.

service.project.licobox.local

When a container exposes a web service, Licobox routes the name to the detected HTTP service, so the URL needs no port.

http://web.licobox.local

Add the port for non-HTTP services, or when a container runs more than one listener:

postgres.shop.licobox.local:5432
A container name does not resolve

Confirm that Container IPs works for the same container. Name routing uses that same network path.

A Compose service uses an unexpected name

Docker Compose derives the project name from the directory that holds the Compose file. Set name: in the Compose file, or pass -p, to choose the project name yourself.

The name opens the wrong service

A container with more than one listener can route to the wrong one. Add the port to the URL when a container runs several services.