Open adamus1red opened 3 years ago
Copying /etc/privoxy/config.new to /etc/privoxy/config allows the build to complete and does apparently create a valid config but there is a fatal error logged regarding it.
In my testing both socks5 9050 and http 8118 proxies both still work
3269adc1794fe9ae8846af60e872b60fc2c1839d26ff3ec194ca579300e06baa
adamus1red@docker125:~ $ docker logs -f 3269adc1794fe9ae8846af60e872b60fc2c1839d26ff3ec194ca579300e06baa
2021-05-29 22:07:44.919 7f955987cb48 Fatal error: can't open configuration file '/etc/privoxy/config': Invalid argument
May 29 22:07:45.927 [notice] Tor 0.4.4.8 running on Linux with Libevent 2.1.12-stable, OpenSSL 1.1.1k, Zlib 1.2.11, Liblzma 5.2.5, and Libzstd 1.4.5.
May 29 22:07:45.927 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning
May 29 22:07:45.927 [notice] Read configuration file "/etc/tor/torrc".
.....
Probably #64 could fix your issue.
@erictroebs #64 does fix the issue. I've got it patched in my fork.
Sorry. I did not notice you are involved in any pull request regarding this issue and I did not check the date either.
@erictroebs @adamus1red
It fixes the build, but breaks privoxy configuration because after that you'll have an empty /etc/privoxy/config
.
Just creating the /etc/privoxy/config
is not enough. Because next you're going to replace some text in it using sed
:
Dockerfile:8. But there is not text to replace in empty file.
When trying to build from the Dockerfile, the build fails due to /etc/privoxy/config not existing.