New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DNS problem #2836
Comments
Any reason you didn’t post the whole log? |
I'm having the same problem. Starting container with revision: 07f5a2b |
Is there a pinned issue for this?
Is there an existing or similar issue/discussion for this?
Is there any comment in the documentation for this?
Is this related to a provider?
Are you using the latest release?
Have you tried using the dev branch latest?
Docker run config used
version: '3.3'
services:
transmission-openvpn:
cap_add:
- NET_ADMIN
volumes:
- '/volume1/docker/transmission-openvpn/data/:/data'
- '/volume1/docker/transmission-openvpn/config/path/:/config'
environment:
- OPENVPN_PROVIDER=NORDVPN
- OPENVPN_CONFIG=france
- OPENVPN_USERNAME=*********
- OPENVPN_PASSWORD=********
- LOCAL_NETWORK=192.168.1.0/24
- NORDVPN_COUNTRY=FR
logging:
driver: json-file
options:
max-size: 10m
ports:
- '9091:9091'
image: haugene/transmission-openvpn
container_name: transmission-vpn
dns:
- '8.8.8.8'
- '8.8.4.4'
security_opt:
- seccomp:unconfined
Current Behavior
Cannot start
Expected Behavior
Start
How have you tried to solve the problem?
I see the pinned post #2410 but it cannot resolve my problem
Log output
Starting container with revision: 07f5a2b
TRANSMISSION_HOME is currently set to: /config/transmission-home
/etc/openvpn/start.sh: line 51: 10 Aborted (core dumped) nslookup ${HEALTH_CHECK_HOST:-"google.com"} > /dev/null 2>&1
WARNING: initial DNS resolution test failed
Creating TUN device /dev/net/tun
Using OpenVPN provider: NORDVPN
Running with VPN_CONFIG_SOURCE auto
Provider NORDVPN has a bundled setup script. Defaulting to internal config
Executing setup script for NORDVPN
/etc/openvpn/nordvpn/..
HW/SW Environment
Anything else?
No response
The text was updated successfully, but these errors were encountered: