Replies: 2 comments 10 replies
-
Yes, use
Here is another example
copy-pasted from here: |
Beta Was this translation helpful? Give feedback.
10 replies
-
The alternative is to disable this pasta (no NAT) mode by using custom pasta options in containers.conf, i.e.
ref #26497 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello everyone,
I have the following situation:
However, another container on the same host cannot reach service1.example.com.
Now I have read that you can access the host with host.internal.container, is there a possibility that service1.example.com can also be accessed via this or how should I solve something like this? The problem is that service1.example.com has a valid certificate, so alternative names like host.internal.container will not work.
Thanks for your help :)
Beta Was this translation helpful? Give feedback.
All reactions