←back to thread

.localhost Domains

(inclouds.space)
301 points todsacerdoti | 6 comments | | HN request time: 1.003s | source | bottom
1. jbverschoor ◴[] No.43645064[source]
Orbstack does all that pretty automatically. It also understands project structure / compose.

https://service.project.orb/

replies(1): >>43646092 #
2. Tokumei-no-hito ◴[] No.43646092[source]
broken link
replies(2): >>43646904 #>>43647072 #
3. zsoltkacsandi ◴[] No.43646904[source]
It was an example how OrbStack puts together the domain.
4. jbverschoor ◴[] No.43647072[source]
Docs at https://docs.orbstack.dev/docker/domains

Forgot to add .local I see

replies(1): >>43652409 #
5. jeroenhd ◴[] No.43652409{3}[source]
I hope Orbstack is also advertising those hostnames on mDNS, because using .local (or, seemingly worse, _relying_ on .local) will conflict with resolver logic on all kinds of devices.
replies(1): >>43653182 #
6. jbverschoor ◴[] No.43653182{4}[source]
I'm not seeing any broadcasts.

What it does is it has a private network for the containers and itself (all containers get their own unique IP, so there's no port mapping needed).

http://orb.local simply lists all running containers.

The host-names are automatically derived from the containername / directoryname / compose project, but you can add other hostnames as well by adding docker labels.

It works really well.