Our great sponsors
-
-
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
I would like to enable certain services to be available only on LAN and access through wireguard, but this 6 year old bug in docker-mac prevents me from writing allow/deny rules in the Nginx. All $remote_addr end up being the docker gateway. I have tried alternatives like podman, colima etc. with similar results for some reason. (rootful, slirp4net options tried). Only thing that resolved to correct $remote_addr was vctl (VMWare’s) but that thing is bare bones compared to any of the others. Any other way to achieve this would be helpful. New to networking scene and starting to learn :)
If you use the nginx-proxy docker image (https://github.com/nginx-proxy/nginx-proxy) then you can just set an environment variable in your docker-compose file: NETWORK_ACCESS=internal
Related posts
- Beginner questions about deploying node.js app on Beanstalk
- Further investigating 403 – access forbidden by rule
- What is the correct way to have my webapp in one container and the webserver in another?
- dockerfile for httpd
- Docker Compose for macvlan and multiple containers sharing the same IP address, but each container uses different ports?