Docker container reboot loop with unauthenticated SOCKS config

[foghorn]

With the latest Docker build that was released, the unauthenticated SOCKS5 proxy configuration no longer works. The container continually reboots and emits the following log message:

Error: REQUIRE_AUTH is true, but PROXY_USER and PROXY_PASSWORD are not set. The application will now exit.

Here's my Docker run command I'm using:

docker run -d --name vpn-socks5
--network=container:vpn
--restart=unless-stopped
serjs/go-socks5-proxy

I tried adding --REQUIRE_AUTH=false but that errored stating that it was not a supported configuration parameter.

[doug-w]

I ran into this today. You have to pass the environment variable. try:

docker run -d --name vpn-socks5 --network=container:vpn --restart=unless-stopped -e REQUIRE_AUTH=false serjs/go-socks5-proxy

It was super annoying to see breaking changes in scripts I haven't touched for months but I guess that's the downside of hoping that you get security updates using the latest tag.

[serjs]

Yea. Latest tag and next release disable by default using socks5 proxy without auth. REQUIRE_AUTH=false may help. Or use tagged release to prevent breaking changes due :latest tags

[KThompson-Lane]

@serjs the docker hub overview tab seems to be out of sync with the README and doesn't mention the new REQUIRE_AUTH environment variable, could you update it to reflect this? I wasn't able to find the GitHub very easily so it took some investigation to realise the issue.