Open cowza opened 2 years ago
I'm having the exact same thing occur to me, time and again on my Synology NAS. In my case, I've re-created the NAS container with the following setup:
--restart=unless-stopped \
--cap-add=NET_ADMIN \
--publish 32785:9117 \
--volume /volume1/configs/jackettvpn:/config \
--env VPN_ENABLED=yes \
--env VPN_TYPE=openvpn \
--env "VPN_OPTIONS=--inactive 3600 --ping 10 --ping-exit 60" \
--env "LAN_NETWORK=192.168.1.0/24" \
--env PUID=1024 \
--env PGID=100 \
--env "TZ=America/New_York" \
--env LEGACY_IPTABLES=1 \
dyonr/jackettvpn
At startup, every single time, the container throws a tantrum about
openvpn: error while loading shared libraries: libnsl.so.1: cannot open shared object file: Permission denied
The only way around it is to stop the container manually, then Editing its docker settings by:
Doing so will keep the jackettvpn container running for a day or so and then once the openvpn session terminates, we will have the exact same problem with Permission denied
(rinse-and-repeat)
I have no idea why this keeps on happening and JackettVPN just continues to exhibit this issue I have another contain with OpenVPN built in (haugene/transmission-openvpn) and although it randomly sees the issue as well, it almost never loses the OpenVPN connection... its been up for days now. I am running DSM 7.0 (not the latest patch).
Any ideas ?
I fixed this by doing recreating the container as follows:
sudo docker run -d --name="jackettvpn" \
--restart unless-stopped \
--cap-add=NET_ADMIN \
--device /dev/net/tun:/dev/net/tun \
--sysctl net.ipv6.conf.all.disable_ipv6=1 \
--publish 9117:9117 \
--volume /path/to/jackettvpn_configs:/config \
--env VPN_ENABLED=yes \
--env VPN_TYPE=openvpn \
--env "VPN_OPTIONS=--inactive 3600 --ping 10 --ping-exit 60" \
--env "LAN_NETWORK=192.168.1.0/24" \
--env PUID=1024 \
--env PGID=100 \
--env "TZ=America/New_York" \
--env LEGACY_IPTABLES=1 \
dyonr/jackettvpn
Turns out running it in elevated privileges was interfering with the setup...
Hi, I'm having a very similar issue as you both were. I know its been a few months, but do you remember what exactly it is you did that fixed it? I don't notice a meaningful difference in your setup or understand what you mean by "running it in elevated privileges was interfering with the setup". Thanks!
Hey there, I get the following error when starting up my container. I've had it working in the past but recently it fails to startup with this permission denied error.
Here is my stack that I'm deploying with docker-compose