How to fix Error response from daemon: failed to create the ipvlan port in Docker

DockerADVANCEDMEDIUMUpdated Jul 5, 2026· 235 views

This error occurs when Docker cannot create an IPvlan network interface, typically due to missing kernel module support, the parent network interface being busy, or running in a virtualized environment that doesn't support IPvlan. Fixing it involves verifying kernel support, checking interface availability, or switching to an alternative network driver like macvlan.

Quick fix

Fixes Error response from daemon: failed to create the ipvlan port

# Check if ipvlan module is loaded
lsmod | grep ipvlan

# Try loading the ipvlan module
sudo modprobe ipvlan

# Verify it loaded successfully
lsmod | grep ipvlan

Verify kernel IPvlan module support
Check if running in a virtual machine
Switch to macvlan as an alternative
Resolve 'device or resource busy' conflicts

docker — error

$# Check if ipvlan module is loaded
lsmod | grep ipvlan
# Try loading the ipvlan module
sudo modprobe ipvlan
# Verify it loaded successfully
lsmod | grep ipvlan
Error response from daemon: failed to create the ipvlan port

What this error means

The "failed to create the ipvlan port" error indicates that Docker was unable to create the necessary network interface for an IPvlan network. IPvlan is a Linux kernel feature that allows multiple virtual interfaces to share a single parent physical interface, with each virtual interface having its own IP address but sharing the same MAC address. This error typically manifests in two forms: - **"operation not supported"**: The Linux kernel doesn't have IPvlan support enabled, or you're running in a virtualized environment (like a VM or container) that doesn't support the required networking capabilities. - **"device or resource busy"**: The parent network interface is already in use by another IPvlan network or another process, or there's a conflict after a system update or reboot. IPvlan networks are commonly used in scenarios requiring: - Direct layer 2 network access without promiscuous mode (unlike macvlan) - Multiple containers with unique IPs on the same physical network segment - Network environments where promiscuous mode is blocked or undesirable The error can occur when creating a new IPvlan network with `docker network create` or when starting a container attached to an existing IPvlan network.

Typical symptoms

Docker commands fail with 'Error response from daemon: failed to create the ipvlan port'
Containers using IPvlan networks fail to start after system update or reboot
Creating IPvlan networks succeeds, but attaching containers fails
'docker network create' with ipvlan driver returns 'operation not supported'
IPvlan networks work on some hosts but not others in the same cluster
Error appears in CI/CD pipelines or containerized environments

Common causes

Linux kernel lacks IPvlan module support (CONFIG_IPVLAN not enabled)
Running inside a virtual machine that doesn't expose IPvlan capabilities
Parent network interface is already in use by another IPvlan network
System reboot or update caused network interface state conflict
Docker version is too old (pre-1.13) with incomplete IPvlan support
Kernel version is below 4.2 where IPvlan support is unstable
Running in a container environment (Docker-in-Docker) without proper privileges
Network namespace conflicts after abnormal Docker daemon shutdown

How to fix "Error response from daemon: failed to create the ipvlan port"

1Verify kernel IPvlan module support

First, check if your Linux kernel has IPvlan support compiled in or available as a module:

bash

# Check if ipvlan module is loaded
lsmod | grep ipvlan

# Try loading the ipvlan module
sudo modprobe ipvlan

# Verify it loaded successfully
lsmod | grep ipvlan

If modprobe ipvlan fails with "Module ipvlan not found", your kernel doesn't have IPvlan support compiled in.

Check kernel configuration:

bash

# Check if CONFIG_IPVLAN is enabled
grep CONFIG_IPVLAN /boot/config-$(uname -r)
# Should show: CONFIG_IPVLAN=m or CONFIG_IPVLAN=y

Check kernel version (IPvlan requires 4.2+):

bash

uname -r
# Should be 4.2 or higher for stable IPvlan support

If your kernel lacks IPvlan support, you'll need to either:
- Upgrade to a kernel with IPvlan compiled in
- Recompile your kernel with CONFIG_IPVLAN=m or CONFIG_IPVLAN=y
- Use an alternative network driver like macvlan

2Check if running in a virtual machine

IPvlan may not work in certain virtualized environments. Check if you're running in a VM:

bash

# Check for virtualization
systemd-detect-virt
# or
cat /sys/class/dmi/id/product_name
# or
hostnamectl | grep -i virtualization

Common VM limitations:
- VMware: May work with proper virtual network configuration
- VirtualBox: Often doesn't support IPvlan properly
- KVM/QEMU: Usually works with virtio network drivers
- Hyper-V: Limited support, may require specific configuration
- OrbStack (macOS): Known to not support IPvlan; use macvlan instead
- WSL2: Limited networking capabilities for advanced drivers

If in a VM, consider alternatives:
1. Use macvlan driver instead of ipvlan
2. Use bridge networking
3. Configure VM networking to support the required features

3Switch to macvlan as an alternative

If IPvlan isn't supported in your environment, macvlan is a viable alternative that provides similar functionality:

IPvlan L2 mode equivalent with macvlan:

bash

# Create macvlan network instead of ipvlan
docker network create -d macvlan \
  --subnet=192.168.1.0/24 \
  --gateway=192.168.1.1 \
  -o parent=eth0 \
  my_macvlan_network

Key differences between IPvlan and Macvlan:
- Macvlan: Each container gets a unique MAC address; requires promiscuous mode on parent
- IPvlan: All containers share the parent's MAC address; no promiscuous mode needed

Enable promiscuous mode for macvlan (if required):

bash

sudo ip link set eth0 promisc on

Note: Some cloud providers and corporate networks block promiscuous mode, making macvlan also unsuitable. In those cases, use bridge networking or an overlay network.

4Resolve 'device or resource busy' conflicts

If the error mentions "device or resource busy", the parent interface may have conflicting state:

Step 1: List existing Docker networks:

bash

docker network ls --filter driver=ipvlan
docker network ls --filter driver=macvlan

Step 2: Remove conflicting networks:

bash

# Stop containers using the network first
docker network disconnect my_ipvlan_network <container_name>

# Remove the network
docker network rm my_ipvlan_network

Step 3: Clean up orphaned network interfaces:

bash

# List network interfaces
ip link show

# Look for ipvlan interfaces (usually named like ipvl0, ipvl1)
# Remove orphaned interfaces manually if needed
sudo ip link delete ipvl0 2>/dev/null

Step 4: Restart Docker daemon:

bash

sudo systemctl restart docker

Step 5: Recreate the network:

bash

docker network create -d ipvlan \
  --subnet=192.168.1.0/24 \
  --gateway=192.168.1.1 \
  -o parent=eth0 \
  my_ipvlan_network

5Verify parent interface exists and is available

The parent interface specified in the IPvlan network must exist and be in the correct state:

List available network interfaces:

bash

ip link show
# or
ip addr show

Check the specific interface you're trying to use:

bash

# Replace 'eth0' with your actual interface name
ip link show eth0

Common interface naming:
- eth0, eth1: Traditional naming
- enp0s3, enp3s0: Predictable interface names
- ens192, ens160: VMware virtual interfaces
- bond0: Bonded interfaces

Create IPvlan with correct parent:

bash

# Find your actual interface name first
ip route | grep default
# Example output: default via 192.168.1.1 dev enp0s3

# Use that interface as parent
docker network create -d ipvlan \
  --subnet=192.168.1.0/24 \
  --gateway=192.168.1.1 \
  -o parent=enp0s3 \
  my_ipvlan_network

For VLAN-tagged interfaces:

bash

# Create VLAN interface first (VLAN 100 on eth0)
sudo ip link add link eth0 name eth0.100 type vlan id 100
sudo ip link set eth0.100 up

# Then use it as parent
docker network create -d ipvlan \
  --subnet=10.100.0.0/24 \
  -o parent=eth0.100 \
  -o ipvlan_mode=l2 \
  vlan100_network

6Upgrade Docker to a recent version

IPvlan support has improved significantly in recent Docker versions. Older versions (pre-1.13, especially experimental releases) may have bugs:

Check current Docker version:

bash

docker version

Upgrade Docker on Ubuntu/Debian:

bash

# Remove old versions
sudo apt remove docker docker-engine docker.io containerd runc

# Set up repository
sudo apt update
sudo apt install ca-certificates curl gnupg
sudo install -m 0755 -d /etc/apt/keyrings
curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo gpg --dearmor -o /etc/apt/keyrings/docker.gpg
sudo chmod a+r /etc/apt/keyrings/docker.gpg

echo "deb [arch=$(dpkg --print-architecture) signed-by=/etc/apt/keyrings/docker.gpg] https://download.docker.com/linux/ubuntu $(. /etc/os-release && echo "$VERSION_CODENAME") stable" | sudo tee /etc/apt/sources.list.d/docker.list > /dev/null

# Install latest Docker
sudo apt update
sudo apt install docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin

Upgrade Docker on CentOS/RHEL:

bash

# Remove old versions
sudo yum remove docker docker-client docker-client-latest docker-common docker-latest docker-latest-logrotate docker-logrotate docker-engine

# Set up repository
sudo yum install -y yum-utils
sudo yum-config-manager --add-repo https://download.docker.com/linux/centos/docker-ce.repo

# Install latest Docker
sudo yum install docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin
sudo systemctl start docker

7Handle post-upgrade or post-reboot issues

After system upgrades or reboots, IPvlan networks may fail due to stale state. Here's how to recover:

Full Docker network cleanup:

bash

# Stop all containers
docker stop $(docker ps -aq)

# Remove all containers
docker rm $(docker ps -aq)

# Remove all networks (except default ones)
docker network prune -f

# Restart Docker
sudo systemctl restart docker

If still failing, perform a more thorough cleanup:

bash

# Stop Docker
sudo systemctl stop docker

# Remove Docker network state files
sudo rm -rf /var/lib/docker/network/files/*

# Start Docker
sudo systemctl start docker

# Recreate your networks
docker network create -d ipvlan \
  --subnet=192.168.1.0/24 \
  --gateway=192.168.1.1 \
  -o parent=eth0 \
  my_ipvlan_network

Persist IPvlan module loading across reboots:

bash

# Add ipvlan to modules loaded at boot
echo "ipvlan" | sudo tee /etc/modules-load.d/ipvlan.conf

8Configure IPvlan in Docker Compose

When using Docker Compose with IPvlan networks, ensure proper configuration:

docker-compose.yml example:

yaml

version: "3.8"

services:
  app:
    image: nginx:alpine
    networks:
      ipvlan_net:
        ipv4_address: 192.168.1.100

networks:
  ipvlan_net:
    driver: ipvlan
    driver_opts:
      parent: eth0
      ipvlan_mode: l2
    ipam:
      config:
        - subnet: 192.168.1.0/24
          gateway: 192.168.1.1

For L3 mode (routing mode):

yaml

networks:
  ipvlan_l3:
    driver: ipvlan
    driver_opts:
      parent: eth0
      ipvlan_mode: l3
    ipam:
      config:
        - subnet: 192.168.10.0/24
        - subnet: 192.168.20.0/24

Important notes for L3 mode:
- No gateway is specified (Docker host acts as router)
- External routing must be configured on your network
- Containers in L3 mode are isolated from the parent network by default

Advanced notes

IPvlan modes explained:

Docker IPvlan supports two modes:

L2 Mode (default):
- Works like macvlan but without unique MAC addresses
- All containers share the parent interface's MAC
- Containers can communicate with the physical network directly
- Suitable for flat network topologies
- Create with: -o ipvlan_mode=l2

L3 Mode:
- Docker host acts as a router between containers and parent network
- Traffic is routed at Layer 3 (IP level), not bridged at Layer 2
- Broadcasts are contained within the container network
- Requires static routes on your gateway for external access
- Better isolation but more complex setup
- Create with: -o ipvlan_mode=l3

Kernel requirements:
- Minimum: Linux kernel 4.2+
- Recommended: Linux kernel 4.9+ for stability
- CONFIG_IPVLAN must be enabled (as module or built-in)
- Docker Swarm mode requires IPvlan support

IPvlan vs Macvlan comparison:

| Feature | IPvlan | Macvlan |
|---------|--------|---------|
| MAC addresses | Shared (parent's MAC) | Unique per container |
| Promiscuous mode | Not required | Required |
| Virtual environments | Less compatible | More compatible |
| Network isolation | Better in L3 mode | Limited |
| Host communication | Blocked by default | Can be configured |

Troubleshooting in enterprise environments:

Some enterprise network switches and cloud providers have restrictions that affect both IPvlan and macvlan:
- Port security limiting MAC addresses per port
- DHCP snooping preventing new MACs
- ARP inspection blocking traffic
- Cloud provider security groups

Container-to-host communication:

By default, containers on IPvlan networks cannot communicate with the Docker host. This is by design for security. If you need host communication:

bash

# Create a separate macvlan/ipvlan interface on the host
ip link add myipvlan link eth0 type ipvlan mode l2
ip addr add 192.168.1.200/24 dev myipvlan
ip link set myipvlan up

Debugging IPvlan issues:

bash

# Check if ipvlan module is loaded
lsmod | grep ipvlan

# View kernel messages for errors
dmesg | grep -i ipvlan
dmesg | tail -50

# Check Docker daemon logs
journalctl -u docker.service -f

# Inspect network details
docker network inspect my_ipvlan_network

# Check network namespace
ip netns list
sudo nsenter --net=/var/run/docker/netns/<container_netns> ip link show

Frequently asked questions

What does "Error response from daemon: failed to create the ipvlan port" mean?: The "failed to create the ipvlan port" error indicates that Docker was unable to create the necessary network interface for an IPvlan network. IPvlan is a Linux kernel feature that allows multiple virtual interfaces to share a single parent physical interface, with each virtual interface having its own IP address but sharing the same MAC address. This error typically manifests in two forms: - "operation not supported": The Linux kernel doesn't have IPvlan support enabled, or you're running in a virtualized environment (like a VM or container) that doesn't support the required networking capabilities.
How do I fix "Error response from daemon: failed to create the ipvlan port"?: This error occurs when Docker cannot create an IPvlan network interface, typically due to missing kernel module support, the parent network interface being busy, or running in a virtualized environment that doesn't support IPvlan. Fixing it involves verifying kernel support, checking interface availability, or switching to an alternative network driver like macvlan.
What causes "Error response from daemon: failed to create the ipvlan port"?: Linux kernel lacks IPvlan module support (CONFIG_IPVLAN not enabled) Running inside a virtual machine that doesn't expose IPvlan capabilities Parent network interface is already in use by another IPvlan network
Is the "Error response from daemon: failed to create the ipvlan port" error serious?: It is a medium-severity error — more of a blocker than a risk. The steps above resolve it.

Official resources & further reading

📚Docker Official Documentation
📖
IPvlan network driver - Docker Docs(Official Docs)
📖
Macvlan network driver - Docker Docs(Official Docs)
📖
Network drivers overview - Docker Docs(Official Docs)
📖
IPvlan - Linux Kernel Documentation(Official Docs)
💬
Docker: Error response from daemon: failed to create the ipvlan port - Docker Forums(Stack Overflow)
💬
Docker: failed to create the ipvlan port: device or resource busy - Unraid Forums(Stack Overflow)
💬
Issues with custom IPVLANL3 Docker network after upgrade - Unraid Forums(Stack Overflow)
🐙
Linux machines does not support docker IPvlan networks - OrbStack GitHub(GitHub)
📖
Configuring IPvlan networking in Docker - 4sysops(Official Docs)
📖
100 Common Docker Errors and Solutions - DEV Community(Official Docs)

How to fix Error response from daemon: failed to create the ipvlan port in Docker

Quick fix

What this error means

Typical symptoms

Common causes

How to fix "Error response from daemon: failed to create the ipvlan port"

Advanced notes

Frequently asked questions

Related errors

Official resources & further reading