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
Describe: container has been running properly for a while. Suddenly container is failing to start with above error. But already provided solution did not help.
2024-03-12T17:28:00Z INFO [routing] default route found: interface eth0, gateway 10.88.0.1, assigned IP 10.88.0.21 and family v4
2024-03-12T17:28:00Z INFO [routing] deleting route for 0.0.0.0/0
2024-03-12T17:28:00Z ERROR creating TUN device file node: file exists
2024-03-12T17:28:00Z INFO Shutdown successful
Investigation done:
Running the container as root.
Validated the correct module and kernel version
rebooted system
listed the loaded module: Noticed that the tun module was not getting loaded during the boot.
Validation:
# lsmod | grep tun <--- returned no output
# ll /dev/net/tun
crw-rw-rw-. 1 root root 10, 200 Mar 11 00:00 /dev/net/tun
manually loaded the module:
# modprob tun
# lsmod | grep tun
tun 73728 0
Post-loading, the container started correctly.
Solution: Load the module during boot:
echo 'tun' > /etc/modules-load.d/tun.conf
cat /etc/modules-load.d/tun.conf
tun
The text was updated successfully, but these errors were encountered:
URL to the Wiki page
https://github.com/qdm12/gluetun-wiki/blob/main/errors/tun.md#creating-tun-device-file-node-file-exists
What's missing?
Describe: container has been running properly for a while. Suddenly container is failing to start with above error. But already provided solution did not help.
Previous issues:
System:
crun
to manage gluetun.Command to run the Gluetun container:
Error:
Investigation done:
root
.tun
module was not getting loaded during the boot.Validation:
manually loaded the module:
Post-loading, the container started correctly.
Solution: Load the module during boot:
The text was updated successfully, but these errors were encountered: