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
podman-compose up
# in other terminal
podman exec -ti try_baz_1 /bin/bash
# install anthing that would trigger dns resolution
apt install telnet
telnet foo
Trying 10.89.1.4...
telnet: Unable to connect to remote host: Connection refused
telnet foo.exmpl
telnet: could not resolve foo.exmpl/telnet: Name or service not known
Expected behavior
The dns names foo.exmpl nd bar.exmpl should be known
I read that links: is supposed to be deprecated and that you should do something with network: instead. However a quick reading of documentation that I found doesn't say how to select the dns names in the way that is done here.
The text was updated successfully, but these errors were encountered:
Describe the bug
I have a docker-compose file with something like this fragment in it:
were the idea is that the address of the "foo" service is available under the dns name "foo.example".
This seems not to work. The services can't find "foo.example", but just plain "foo" is resolvable.
To Reproduce
docker-compose.yml:
Expected behavior
The dns names
foo.exmpl
ndbar.exmpl
should be knownActual behavior
They are not.
Output
Environment:
Additional context
I read that
links:
is supposed to be deprecated and that you should do something withnetwork:
instead. However a quick reading of documentation that I found doesn't say how to select the dns names in the way that is done here.The text was updated successfully, but these errors were encountered: