We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is your feature request related to a problem? Please describe. Having an issue communicating between containers which orbstack doesn't really solve.
I used to use a reverse proxy which handled all the SSL, but now I'm trying to have this centralised in orbstack.
Communication between host works fine i.e. https://container.orb.local resolves SSL perfectly.
However within containera.orb.local I'm trying to call https://containerb.orb.local, there is no port 443 listening of course, so this doesn't work.
This is because within containers speaking to another container only resolves the actual ports it's listening to, i.e. the raw ports.
Describe the solution you'd like Realistically .local should be similar within containers as it is host>container.
.local
If needed "ports" could still be possible using docker network and communicating via the container name directly (i.e. http://localstack:4566).
Ideally there would also be a path in which the SSL cert can easily be accessed to it can be added into the certificate chains of all containers.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Is your feature request related to a problem? Please describe.
Having an issue communicating between containers which orbstack doesn't really solve.
I used to use a reverse proxy which handled all the SSL, but now I'm trying to have this centralised in orbstack.
Communication between host works fine i.e. https://container.orb.local resolves SSL perfectly.
However within containera.orb.local I'm trying to call https://containerb.orb.local, there is no port 443 listening of course, so this doesn't work.
This is because within containers speaking to another container only resolves the actual ports it's listening to, i.e. the raw ports.
Describe the solution you'd like
Realistically
.local
should be similar within containers as it is host>container.If needed "ports" could still be possible using docker network and communicating via the container name directly (i.e. http://localstack:4566).
Ideally there would also be a path in which the SSL cert can easily be accessed to it can be added into the certificate chains of all containers.
The text was updated successfully, but these errors were encountered: