Skip to content

WSL2 Kernel 6.1.102: iptables "raw" table does not exist, blocking Docker networking #14487

@jvm-bot

Description

@jvm-bot

Windows Version

Microsoft Windows [Version 00.26200.8037]

WSL Version

2.6.3.0

Are you using WSL 1 or WSL 2?

  • WSL 2
  • WSL 1

Kernel Version

6.6.87.2-1

Distro Version

Ubuntu 24.04

Other Software

Report: Persistent Docker Networking Issue in WSL2 Ubuntu

Problem Description

figenergy@DESKTOP-N1JEVHI:~$

Plain Text

docker: Error response from daemon: failed to set up container networking: failed to create endpoint <container_name> on network bridge: Unable to enable DIRECT ACCESS FILTERING - DROP rule: (iptables failed: iptables --wait -t raw -A PREROUTING -d 172.17.0.2 ! -i docker0 -j DROP: iptables v1.8.7 (legacy): can't initialize iptables table `raw': Table does not exist (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
(exit status 3))

This issue prevents any Docker-dependent applications, such as OpenShell Gateway and NemoClaw, from functioning correctly within the WSL2 environment.

Environment Details


Operating System: Windows 11 (User's system)


WSL2 Distribution: Ubuntu 22.04 LTS


Docker Desktop Version: 28.2.2 (as verified in WSL2 terminal)


WSL Kernel Version: 6.1.102 (as verified by uname -a in WSL2 terminal)

Troubleshooting Steps Taken (Chronological Order)

Initial Diagnosis: Identified that nemoclaw onboard was failing with a 403 Forbidden error, which was traced back to Docker networking issues and the iptables error.

NemoClaw/OpenShell Reinstallation Attempts: Attempted to reinstall openshell and nemoclaw tools within the existing WSL2 Ubuntu environment.

Docker Client Installation/Verification (Initial): Installed docker.io and added user to docker group in the initial WSL2 Ubuntu environment. Verified docker --version but openshell gateway start failed with the iptables error.

iptables Legacy Mode Attempt: Attempted to switch iptables to legacy mode (sudo update-alternatives --set iptables /usr/sbin/iptables-legacy) and restarted Docker service, but the iptables error persisted.

Full Docker Desktop Reinstallation (Windows Side):


Instructed user to set Windows sleep to "Never".


Instructed user to completely uninstall Docker Desktop from Windows.


Instructed user to restart Windows.


Instructed user to reinstall Docker Desktop on Windows, ensuring WSL2 integration for Ubuntu was enabled.

WSL2 Ubuntu Distribution Reinstallation:


Instructed user to back up any important data from the existing WSL2 Ubuntu distribution (user confirmed no critical data).


Instructed user to terminate the existing Ubuntu distribution (wsl --terminate Ubuntu).


Instructed user to unregister the existing Ubuntu distribution (wsl --unregister Ubuntu).


Instructed user to select "Skip WSL distro integration" in Docker Desktop pop-up after termination.


Instructed user to reinstall "Ubuntu 22.04" from the Microsoft Store.


Instructed user to complete initial Ubuntu setup (username/password).

Docker Client Reinstallation (New WSL2 Ubuntu):


Executed sudo apt-get update.


Executed sudo apt-get install -y docker.io.


Executed sudo usermod -aG docker $USER.


Instructed user to close and reopen the Ubuntu terminal for group changes to take effect.

Docker Functionality Verification (New WSL2 Ubuntu):


Verified docker --version (output: Docker version 28.2.2, build 28.2.2-0ubuntu1~22.04.1).


Attempted to run docker run hello-world, which resulted in the same iptables error as described above.

Observed Behavior

The iptables error persists even after a complete reinstallation of Docker Desktop on Windows and a fresh installation of the WSL2 Ubuntu distribution. This suggests a deeper issue with the WSL2 environment's kernel or its interaction with Docker's networking components.

Request for Assistance

I am seeking assistance to diagnose and resolve this persistent iptables error, which is preventing Docker from functioning correctly within my WSL2 Ubuntu environment. The goal is to enable Docker to run containers without this networking failure, thereby allowing the subsequent setup of OpenShell Gateway and NemoClaw. Any guidance or specific troubleshooting steps would be greatly appreciated.

Author: Manus AI

Date: March 19, 2026

Repro Steps

Report: Persistent Docker Networking Issue in WSL2 Ubuntu

Problem Description

figenergy@DESKTOP-N1JEVHI:~$

Plain Text

docker: Error response from daemon: failed to set up container networking: failed to create endpoint <container_name> on network bridge: Unable to enable DIRECT ACCESS FILTERING - DROP rule: (iptables failed: iptables --wait -t raw -A PREROUTING -d 172.17.0.2 ! -i docker0 -j DROP: iptables v1.8.7 (legacy): can't initialize iptables table `raw': Table does not exist (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
(exit status 3))

This issue prevents any Docker-dependent applications, such as OpenShell Gateway and NemoClaw, from functioning correctly within the WSL2 environment.

Environment Details


Operating System: Windows 11 (User's system)


WSL2 Distribution: Ubuntu 22.04 LTS


Docker Desktop Version: 28.2.2 (as verified in WSL2 terminal)


WSL Kernel Version: 6.1.102 (as verified by uname -a in WSL2 terminal)

Troubleshooting Steps Taken (Chronological Order)

Initial Diagnosis: Identified that nemoclaw onboard was failing with a 403 Forbidden error, which was traced back to Docker networking issues and the iptables error.

NemoClaw/OpenShell Reinstallation Attempts: Attempted to reinstall openshell and nemoclaw tools within the existing WSL2 Ubuntu environment.

Docker Client Installation/Verification (Initial): Installed docker.io and added user to docker group in the initial WSL2 Ubuntu environment. Verified docker --version but openshell gateway start failed with the iptables error.

iptables Legacy Mode Attempt: Attempted to switch iptables to legacy mode (sudo update-alternatives --set iptables /usr/sbin/iptables-legacy) and restarted Docker service, but the iptables error persisted.

Full Docker Desktop Reinstallation (Windows Side):


Instructed user to set Windows sleep to "Never".


Instructed user to completely uninstall Docker Desktop from Windows.


Instructed user to restart Windows.


Instructed user to reinstall Docker Desktop on Windows, ensuring WSL2 integration for Ubuntu was enabled.

WSL2 Ubuntu Distribution Reinstallation:


Instructed user to back up any important data from the existing WSL2 Ubuntu distribution (user confirmed no critical data).


Instructed user to terminate the existing Ubuntu distribution (wsl --terminate Ubuntu).


Instructed user to unregister the existing Ubuntu distribution (wsl --unregister Ubuntu).


Instructed user to select "Skip WSL distro integration" in Docker Desktop pop-up after termination.


Instructed user to reinstall "Ubuntu 22.04" from the Microsoft Store.


Instructed user to complete initial Ubuntu setup (username/password).

Docker Client Reinstallation (New WSL2 Ubuntu):


Executed sudo apt-get update.


Executed sudo apt-get install -y docker.io.


Executed sudo usermod -aG docker $USER.


Instructed user to close and reopen the Ubuntu terminal for group changes to take effect.

Docker Functionality Verification (New WSL2 Ubuntu):


Verified docker --version (output: Docker version 28.2.2, build 28.2.2-0ubuntu1~22.04.1).


Attempted to run docker run hello-world, which resulted in the same iptables error as described above.

Observed Behavior

The iptables error persists even after a complete reinstallation of Docker Desktop on Windows and a fresh installation of the WSL2 Ubuntu distribution. This suggests a deeper issue with the WSL2 environment's kernel or its interaction with Docker's networking components.

Request for Assistance

I am seeking assistance to diagnose and resolve this persistent iptables error, which is preventing Docker from functioning correctly within my WSL2 Ubuntu environment. The goal is to enable Docker to run containers without this networking failure, thereby allowing the subsequent setup of OpenShell Gateway and NemoClaw. Any guidance or specific troubleshooting steps would be greatly appreciated.

Author: Manus AI

Date: March 19, 2026

Expected Behavior

Report: Persistent Docker Networking Issue in WSL2 Ubuntu

Problem Description

figenergy@DESKTOP-N1JEVHI:~$

Plain Text

docker: Error response from daemon: failed to set up container networking: failed to create endpoint <container_name> on network bridge: Unable to enable DIRECT ACCESS FILTERING - DROP rule: (iptables failed: iptables --wait -t raw -A PREROUTING -d 172.17.0.2 ! -i docker0 -j DROP: iptables v1.8.7 (legacy): can't initialize iptables table `raw': Table does not exist (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
(exit status 3))

This issue prevents any Docker-dependent applications, such as OpenShell Gateway and NemoClaw, from functioning correctly within the WSL2 environment.

Environment Details


Operating System: Windows 11 (User's system)


WSL2 Distribution: Ubuntu 22.04 LTS


Docker Desktop Version: 28.2.2 (as verified in WSL2 terminal)


WSL Kernel Version: 6.1.102 (as verified by uname -a in WSL2 terminal)

Troubleshooting Steps Taken (Chronological Order)

Initial Diagnosis: Identified that nemoclaw onboard was failing with a 403 Forbidden error, which was traced back to Docker networking issues and the iptables error.

NemoClaw/OpenShell Reinstallation Attempts: Attempted to reinstall openshell and nemoclaw tools within the existing WSL2 Ubuntu environment.

Docker Client Installation/Verification (Initial): Installed docker.io and added user to docker group in the initial WSL2 Ubuntu environment. Verified docker --version but openshell gateway start failed with the iptables error.

iptables Legacy Mode Attempt: Attempted to switch iptables to legacy mode (sudo update-alternatives --set iptables /usr/sbin/iptables-legacy) and restarted Docker service, but the iptables error persisted.

Full Docker Desktop Reinstallation (Windows Side):


Instructed user to set Windows sleep to "Never".


Instructed user to completely uninstall Docker Desktop from Windows.


Instructed user to restart Windows.


Instructed user to reinstall Docker Desktop on Windows, ensuring WSL2 integration for Ubuntu was enabled.

WSL2 Ubuntu Distribution Reinstallation:


Instructed user to back up any important data from the existing WSL2 Ubuntu distribution (user confirmed no critical data).


Instructed user to terminate the existing Ubuntu distribution (wsl --terminate Ubuntu).


Instructed user to unregister the existing Ubuntu distribution (wsl --unregister Ubuntu).


Instructed user to select "Skip WSL distro integration" in Docker Desktop pop-up after termination.


Instructed user to reinstall "Ubuntu 22.04" from the Microsoft Store.


Instructed user to complete initial Ubuntu setup (username/password).

Docker Client Reinstallation (New WSL2 Ubuntu):


Executed sudo apt-get update.


Executed sudo apt-get install -y docker.io.


Executed sudo usermod -aG docker $USER.


Instructed user to close and reopen the Ubuntu terminal for group changes to take effect.

Docker Functionality Verification (New WSL2 Ubuntu):


Verified docker --version (output: Docker version 28.2.2, build 28.2.2-0ubuntu1~22.04.1).


Attempted to run docker run hello-world, which resulted in the same iptables error as described above.

Observed Behavior

The iptables error persists even after a complete reinstallation of Docker Desktop on Windows and a fresh installation of the WSL2 Ubuntu distribution. This suggests a deeper issue with the WSL2 environment's kernel or its interaction with Docker's networking components.

Request for Assistance

I am seeking assistance to diagnose and resolve this persistent iptables error, which is preventing Docker from functioning correctly within my WSL2 Ubuntu environment. The goal is to enable Docker to run containers without this networking failure, thereby allowing the subsequent setup of OpenShell Gateway and NemoClaw. Any guidance or specific troubleshooting steps would be greatly appreciated.

Author: Manus AI

Date: March 19, 2026

Actual Behavior

Report: Persistent Docker Networking Issue in WSL2 Ubuntu

Problem Description

figenergy@DESKTOP-N1JEVHI:~$

Plain Text

docker: Error response from daemon: failed to set up container networking: failed to create endpoint <container_name> on network bridge: Unable to enable DIRECT ACCESS FILTERING - DROP rule: (iptables failed: iptables --wait -t raw -A PREROUTING -d 172.17.0.2 ! -i docker0 -j DROP: iptables v1.8.7 (legacy): can't initialize iptables table `raw': Table does not exist (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
(exit status 3))

This issue prevents any Docker-dependent applications, such as OpenShell Gateway and NemoClaw, from functioning correctly within the WSL2 environment.

Environment Details


Operating System: Windows 11 (User's system)


WSL2 Distribution: Ubuntu 22.04 LTS


Docker Desktop Version: 28.2.2 (as verified in WSL2 terminal)


WSL Kernel Version: 6.1.102 (as verified by uname -a in WSL2 terminal)

Troubleshooting Steps Taken (Chronological Order)

Initial Diagnosis: Identified that nemoclaw onboard was failing with a 403 Forbidden error, which was traced back to Docker networking issues and the iptables error.

NemoClaw/OpenShell Reinstallation Attempts: Attempted to reinstall openshell and nemoclaw tools within the existing WSL2 Ubuntu environment.

Docker Client Installation/Verification (Initial): Installed docker.io and added user to docker group in the initial WSL2 Ubuntu environment. Verified docker --version but openshell gateway start failed with the iptables error.

iptables Legacy Mode Attempt: Attempted to switch iptables to legacy mode (sudo update-alternatives --set iptables /usr/sbin/iptables-legacy) and restarted Docker service, but the iptables error persisted.

Full Docker Desktop Reinstallation (Windows Side):


Instructed user to set Windows sleep to "Never".


Instructed user to completely uninstall Docker Desktop from Windows.


Instructed user to restart Windows.


Instructed user to reinstall Docker Desktop on Windows, ensuring WSL2 integration for Ubuntu was enabled.

WSL2 Ubuntu Distribution Reinstallation:


Instructed user to back up any important data from the existing WSL2 Ubuntu distribution (user confirmed no critical data).


Instructed user to terminate the existing Ubuntu distribution (wsl --terminate Ubuntu).


Instructed user to unregister the existing Ubuntu distribution (wsl --unregister Ubuntu).


Instructed user to select "Skip WSL distro integration" in Docker Desktop pop-up after termination.


Instructed user to reinstall "Ubuntu 22.04" from the Microsoft Store.


Instructed user to complete initial Ubuntu setup (username/password).

Docker Client Reinstallation (New WSL2 Ubuntu):


Executed sudo apt-get update.


Executed sudo apt-get install -y docker.io.


Executed sudo usermod -aG docker $USER.


Instructed user to close and reopen the Ubuntu terminal for group changes to take effect.

Docker Functionality Verification (New WSL2 Ubuntu):


Verified docker --version (output: Docker version 28.2.2, build 28.2.2-0ubuntu1~22.04.1).


Attempted to run docker run hello-world, which resulted in the same iptables error as described above.

Observed Behavior

The iptables error persists even after a complete reinstallation of Docker Desktop on Windows and a fresh installation of the WSL2 Ubuntu distribution. This suggests a deeper issue with the WSL2 environment's kernel or its interaction with Docker's networking components.

Request for Assistance

I am seeking assistance to diagnose and resolve this persistent iptables error, which is preventing Docker from functioning correctly within my WSL2 Ubuntu environment. The goal is to enable Docker to run containers without this networking failure, thereby allowing the subsequent setup of OpenShell Gateway and NemoClaw. Any guidance or specific troubleshooting steps would be greatly appreciated.

Author: Manus AI

Date: March 19, 2026

Diagnostic Logs

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions