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
What is the problem you're trying to solve
Have Compose manage interaction with ports on the local machine, and on remote ports as well.
Describe the solution you'd like
Be able to define services that are mappings to url (including localhost) and to one or more ports on that URL. I'd like to not have to need to worry about the correct networking mode to access ports, e.g. on a locally running service.
For example, say I have a locally running Postgres on my machine. I don't want to make a Postgres Docker container, as it's inefficient and managing state with Docker can be a small mental overhead. Instead of working out the correct networking mode, I'd love to be able to say something like the following:
Another similar use case might be in something like GitLab CI/CD, where using their services concept alongside tests running in Docker Compose is currently difficult. Being able to easily break out of Docker Compose to a local port word be helpful.
Finally, this would be great for production deployments re: security. Having a local-only network whose exits are explicitly defined would make standardisation of tooling that inspects said exits much simpler.
The text was updated successfully, but these errors were encountered:
robertlagrant
changed the title
Allow Compose to define externally accessible resources as internal services
Allow Compose to define externally accessible resources as Docker Compose services
Jun 14, 2023
What is the problem you're trying to solve
Have Compose manage interaction with ports on the local machine, and on remote ports as well.
Describe the solution you'd like
Be able to define services that are mappings to url (including localhost) and to one or more ports on that URL. I'd like to not have to need to worry about the correct networking mode to access ports, e.g. on a locally running service.
For example, say I have a locally running Postgres on my machine. I don't want to make a Postgres Docker container, as it's inefficient and managing state with Docker can be a small mental overhead. Instead of working out the correct networking mode, I'd love to be able to say something like the following:
Another similar use case might be in something like GitLab CI/CD, where using their services concept alongside tests running in Docker Compose is currently difficult. Being able to easily break out of Docker Compose to a local port word be helpful.
Finally, this would be great for production deployments re: security. Having a local-only network whose exits are explicitly defined would make standardisation of tooling that inspects said exits much simpler.
The text was updated successfully, but these errors were encountered: