search

binhex / arch-privoxyvpn

Docker build script for Arch Linux base with Privoxy and OpenVPN
GNU General Public License v3.0
102 stars 24 forks source link

microsocks does not start automatically #6

Closed ghost closed 3 years ago

ghost commented 3 years ago

After container comes up, microsocks does not start automatically. If I start it manually using /home/nobody/microsocks.sh, it works fine, and accepts the credentials passed at the host CLI:

docker run -d \ --sysctl="net.ipv4.conf.all.src_valid_mark=1" \ --privileged=true \ --name=microsocks \ -p 59118:9118 \ -v /opt/microsocks:/config \ -v /etc/localtime:/etc/localtime:ro \ -e VPN_ENABLED=yes \ -e VPN_PROV=custom \ -e VPN_CLIENT=wireguard \ -e LAN_NETWORK=192.168.1.0/24 \ -e NAME_SERVERS=1.1.1.1,1.0.0.1 \ -e SOCKS_USER=johndoe \ -e SOCKS_PASS=testing \ -e ENABLE_SOCKS=yes \ -e ENABLE_PRIVOXY=no \ -e DEBUG=true \ -e UMASK=007 \ -e PUID=1000 \ -e PGID=1000 \ binhex/arch-privoxyvpn

I do not know believe it is related, as wireguard appears to be working fine, but I also noticed a rapidly growing supervisord.log file under the mapped /config with these two lines repeating in it: 2020-11-17 15:01:45,990 DEBG 'watchdog-script' stderr output: cat: /tmp/getiptables: Permission denied

ghost commented 3 years ago

Mea culpa. Using UMASK=000 resolved the issue with the startup of microsocks, and errors in the log file.