You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
By default, every container joins an application-wide default network, and is discoverable at a hostname that’s the same as the service name. This means links are largely unnecessary.
In hyper however it only seems to work if the link is explicitly specified.
For example in following compose file the links should not be necessary:
I got your concern. The hyper compose does not have a default hostname same as service name, it will use the prefix of container ID as the hostname if you do not specify.
We will consider to implement it, just created a feature request to log this: hyperhq/hypercli#240.
I mean you claim to be compatible with docker compose, but I had to change so many things from my compose file, that I'd consider it another language.
You should really get this right as I think for many it's the most compelling argument to use hyper.sh.
From https://docs.docker.com/compose/compose-file/compose-versioning:
In hyper however it only seems to work if the link is explicitly specified.
For example in following compose file the links should not be necessary:
The text was updated successfully, but these errors were encountered: