For containers that want docker socket volume mounts, how do you point them to docker-socket-proxy?

[SawkeeReemo]

Sorry, bit of a newb on this specific service. I learned about docker-socket-proxy while installing Homepage, and I'm here wondering how I point other containers, like Glances system monitoring service, to this proxy service when they are looking to volume mount my docker socket. Do you mount something from docker-socket-proxy's volumes instead? Not sure how to use this with other services since it seems to be a function built into Homepage's config instead of a compose env var or vomume mount.

[shalafi99]

Usage of the docker socket proxy implies in switching from a direct volume access to the HTTP protocol (TCP socket).
If the app running inside the container will not support usage of this variable:

    environment:
      - DOCKER_HOST=tcp://docker-proxy:2375

or configuring the proxy address/port directly in its config, it might not be compatible with proxy usage.

For your particular example, I never used Glance so I looked up its doc page, did not see an explicit mention of using this environment variable. Then I did a more general search and the results indicated it should support it.

[Eirikr70]

Hello @SawkeeReemo I think that this information would be relevant to insert in the documentation. I have had to ask an AI to figure out how to configure Crowdsec (DOCKER_HOST: tcp://socketproxy:2375), Uptime-kuma (new parameter in the UI), Beszel-agent (publication of the port on the host and DOCKER_HOST: tcp://127.0.0.1:2375) and Watchtower (like Crowdsec, and configuration with MONITOR_ONLY). If that is ok with you I can write an add-on to the documentation and propose it in a PR.