One reason I'm still using docker desktop in my (small) company is that our production systems are using docker compose and the networking with domains does not translate 1:1 between orbstack locally and docker compose + nginx in production. Is there an easy way to solve this?
OrbStack domains can be nice but you don't have to use them. It's fully compatible with Compose, so you can just run the same commands with no changes to your setup. Did that not work for you?
I don't fully remember the issues, but I think it was somehow necessary to run all apps on port 80 inside of the containers in order to make the OrbStack domains work properly.
I do remember now. It was about container-to-container-communication: having FQDN is awesome because it helps you not to care about quirks of localhost:PORT everywhere in your code (SSL out of the box would be great, though). The problem is that, other than real world FQDN, the domain name of container A is not available inside of container B. This breaks frontend frameworks like next or nuxt which combine SSR on the first page load and do CSR on subsequent request: on the server, the API domain would be `host.docker.internal` and would need to change to `http://api.orb.local` for the client side. The docs didn't make this clear, so at first, I refactored everything to use the orbstack url, just to return back to the mix.
