VPN is only able to connect when run using a root podman container #2342
-
Hi everyone, I'm trying to set up a container for Gluetun using the following configuration. I'm using NordVPN with WireGuard. However, I'm having trouble getting it to work correctly. Here is my current gluetun.yaml: version: "3"
services:
gluetun:
image: ghcr.io/qdm12/gluetun
network_mode: bridge
container_name: gluetun
cap_add: [NET_ADMIN, NET_RAW]
environment:
- VPN_SERVICE_PROVIDER=nordvpn
- VPN_TYPE=wireguard
- WIREGUARD_PRIVATE_KEY=<REDACTED>
- WIREGUARD_ALLOWED_IPS=0.0.0.0/0
- TZ=Europe/London
- UPDATER_PERIOD=24h
- SERVER_CITIES=london
- PUID=1000
- PGID=1000
devices:
- /dev/net/tun:/dev/net/tun
sysctls:
- net.ipv6.conf.all.disable_ipv6=1
- net.ipv4.conf.all.src_valid_mark=1
ports:
- 51821:51820/udp
volumes:
- gluetun-config:/gluetun
volumes:
gluetun-config: Issues I'm Facing:
Additional Information:
Logs from Running
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
Wrong
I've run it with the |
Beta Was this translation helpful? Give feedback.
I do not have any other containers running, but I do have WireGuard running on the host machine. Using the privileged flag did not work for me, I think my issue is related to Podman's use of Pasta as the default network tool instead of Slirp4netns. My old container would have still used Slirp4netns while Gluetun would use Pasta as my nordlynx container was created using podman 4.
Using the following configuration allows Gluetun to connect with the existing compose file:
I have also gotten Pasta to work with these settings: