generic error (-101): Network is unreachable #2894
Comments
|
I also ran into this recently - odd since I tried a couple older image tags and the same error pops up. I use arch, Docker version 27.3.1. I will look into this when I have time. |
|
Update: I found that this workaround solves the issue when using Docker Desktop for MacOS. Unfortunately I prefer OrbStack so I'm still trying to figure that out. |
|
+1 error just popped up for me after 1+ year of reliable service. no config changes ubuntu. kernel: 6.8.0-49-generic as a workaround you can add |
|
So the error message and things I googled went over my head. That said, I believe running this script got me up and running again. There may have been other things that are also necessary - I wasn't procedural when debugging this #!/bin/sh
# Create the necessary file structure for /dev/net/tun
if ( [ ! -c /dev/net/tun ] ); then
if ( [ ! -d /dev/net ] ); then
mkdir -m 755 /dev/net
fi
mknod /dev/net/tun c 10 200
chmod 0755 /dev/net/tun
fi
# Load the tun module if not already loaded
if ( !(lsmod | grep -q "^tun\s") ); then
insmod /usr/lib/modules/6.11.8-arch1-2/kernel/drivers/net/tun.ko.zst
fi |
|
The |
|
I added UPDATE: after upgrading from Ubuntu 22.04 to 24.04, it started failing again and per chatGPT's suggestion I ran: and it worked again |
|
Strange, I've been running my ubuntu server now for 5 years and never had to redo the permissions after an os update. |
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
Current Behavior
Transmission fails to launch
Expected Behavior
Transmission should launch
How have you tried to solve the problem?
I've tried manually setting DNS, setting OPENVPN_OPTS, disabling CREATE_TUNs_DEVICE, running in privileged mode etc.
Log output
HW/SW Environment
Anything else?
Transmission was previously working fine with the config above until recently.
The text was updated successfully, but these errors were encountered: