Closed LarsaSolidor closed 3 years ago
check #1355 , think this might help
check #1355 , think this might help
The --sysctl net.ipv6.conf.all.disable_ipv6=0
fix suggested in #1355 hasn't resolved the issue.
Likely this is the same issue that has been plaguing transmission-vpn on PIA since the fall where no trackers can be contacted after initial container creation/start. Can replicate at will and I am not experiencing the ipv6 route add permission denied result on my environment:
dc stop transmission-vpn dc up -d transmission-vpn [All scrape attempts to http and udp trackers will with 'cannot connect', indefinitely] dc restart transmission-vpn [trackers immediately scrape, voila. Until next time]
Of course this was all recently exacerbated by #1725, back to above after the fix w/adding --dhcp-option DNS 8.8.8.8 to the OPENVPN_OPTS documented there.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
Still an issue. Every time my containers update themselves, I have to issue a docker-compose restart on transmission-vpn to get DNS resolution working.
still an issue
is this still an issue with the dev branch? dev is based on ubuntu and has fixed a few dns issues..
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
Looks like dev has gone to latest now. I just did some testing and my recreate from above now works fine - no longer requiring a restart for UDP trackers to work. Seems fixed from what I can tell.
same issue here
Before creating this issue I have:
Describe the problem
When new torrents are added to transmission, they do not download until the container is restarted. They begin downloading immediately after a container restart.
Add your docker run command or docker-compose file
Logs
Host system: