You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a connection issue since Gluetun is somehow trying to use the network interface which dose not have link (eth0 not having link is by my choice and design) also it has "unhealthy" status..
Please correct me if I'm wrong but shouldn't Gluetun use the default Docker interface (and I think the Bridge aka docker0)?
Or is the problem the fact that the .yml "devices" is point to /dev/net/tun if so, how would I go about and influence this?
I'll try to keep this short but also provide info so those of you who actually know what you are doing (basically 99.99% of every user out there) can glance at this and hopefully help me or push me in the right path for a solution.
I truly appreciate the inputs.
route show
default via 10.0.0.1 dev eth1 proto dhcp src 10.0.0.10 metric 100
10.0.0.0/24 dev eth1 proto kernel scope link src 10.0.0.10 metric 100
172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown
172.18.0.0/16 dev br-166aeed9a694 proto kernel scope link src 172.18.0.1 linkdown
Docker version 26.1.1, build 4cf5afa
Docker Compose version v2.27.0
REPOSITORY TAG IMAGE ID CREATED SIZE
qmcgaw/gluetun latest 5c3c0f94f6c6 44 hours ago 51MB
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
cd7af6ba407d qmcgaw/gluetun:latest "/gluetun-entrypoint" 18 minutes ago Exited (0) 18 minutes ago gluetun
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi guys,
I have a connection issue since Gluetun is somehow trying to use the network interface which dose not have link (eth0 not having link is by my choice and design) also it has "unhealthy" status..
Please correct me if I'm wrong but shouldn't Gluetun use the default Docker interface (and I think the Bridge aka docker0)?
Or is the problem the fact that the .yml "devices" is point to
/dev/net/tun
if so, how would I go about and influence this?I'll try to keep this short but also provide info so those of you who actually know what you are doing (basically 99.99% of every user out there) can glance at this and hopefully help me or push me in the right path for a solution.
I truly appreciate the inputs.
route show
docker -v; docker compose version; docker image ls; docker ps -a
cat ~/docker/gluetun/docker-compose.yml
And here is error log when i run it with
docker compose up
Beta Was this translation helpful? Give feedback.
All reactions