Amanda Wee

I am facing the same issue. If I specify `new_group_delay = 120` only, I end up with a plan that includes: ``` + new_group_delay = 120 + new_host_delay = 300...

@wollomatic would you be open to @chrishoage's suggestion of using labels? I was intrigued by the idea and have a proof of concept running, though I'm still working on automatically...

Here's my proof of concept: https://github.com/amanda-wee/socket-proxy/tree/per-container-allowlists I added a dependency on the Docker API SDK for Go. If necessary, it should be possible to rework the code to do without...

@edekeijzer yes, I have been testing with a name explicitly specified in compose.yaml as `container_name: beszel-socket-proxy`, and just tried with leaving it out and using the service name (`socket-proxy`, or...

@edekeijzer thanks for testing. I guess the core is checking that the per-container allowlists come into effect correctly for the given containers, whether the socket proxy starts before or after...

@wollomatic I have created another branch from my per-container-allowlists branch for investigating integrating the parts of the Docker SDK for Go needed to get the functionality to work. See: https://github.com/amanda-wee/socket-proxy/tree/per-container-allowlists-integrate-sdk...

> it's been running with Traefik, Watchtower and Gitea ACT Runner for two weeks now and I haven't seen any issues. Awesome. I haven't seen issues with Beszel either, also...

I've made some optimisations to reduce the number of Docker API calls and data received from the Docker API, and merged the whole Docker SDK integration into my original `per-container-allowlists`...

@wollomatic great, here's the pull request! https://github.com/wollomatic/socket-proxy/pull/69

Thanks friends. I'm running Beszel agent via Docker on Ubuntu 24.04 with a NUC 13 i5 (the hub is on a RPi 5), and got this warning and no GPU...