Can someone please guide me how to enable certain containers to be available only on LAN, without allow/deny rules in the Nginx?

This page summarizes the projects mentioned and recommended in the original post on

Our great sponsors
  • - Download’s Tech Salary Report
  • InfluxDB - Build time-series-based applications quickly and at scale.
  • Scout APM - Truly a developer’s best friend
  • SonarLint - Clean code begins in your IDE with SonarLint
  • for-mac

    Bug reports for Docker Desktop for Mac

    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 :)

  • nginx-proxy

    Automated nginx proxy for Docker containers using docker-gen

    If you use the nginx-proxy docker image ( then you can just set an environment variable in your docker-compose file: NETWORK_ACCESS=internal


    Download’s Tech Salary Report. Median salaries, most in-demand technologies, state of the remote work... all you need to know your worth on the market by tech recruitment platform

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts