Skip to content
New issue

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

Using CDP as a reverse proxy for non-docker services - is it possible? #640

Closed
AlexPewMaster opened this issue Jul 5, 2024 · 2 comments
Closed

Comments

@AlexPewMaster
Copy link

Hi, I would like to use this as my reverse proxy. I have many Docker containers running on the same machine that's also running a reverse proxy, but I also have a tunnel for other services that run on a different machine. Is there a way that I can configure parts of CDP to proxy some things to localhost without a Docker container to attach the labels to?

@francislavoie
Copy link
Collaborator

Yes it's possible. You can either put labels right on your CDP container itself, or provide a base Caddyfile (see env config options).

It wouldn't be localhost though, because localhost means "connect to this same container". Containers are isolated from the host. You would connect to host.docker.internal instead (Google it for more details).

@ksurl
Copy link

ksurl commented Aug 19, 2024

you can use a placeholder container with labels to point to an external host ip. a lightweight option could be a busybox container with no networking and set to run tail -f /dev/null to stay running.

@francislavoie francislavoie closed this as not planned Won't fix, can't repro, duplicate, stale Aug 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants