FS#50747 - [docker] Could not create ipvlan network
Attached to Project:
Community Packages
Opened by zml.xyz (zml.xyz) - Monday, 12 September 2016, 03:52 GMT
Last edited by Doug Newgard (Scimmia) - Wednesday, 21 September 2016, 04:02 GMT
Opened by zml.xyz (zml.xyz) - Monday, 12 September 2016, 03:52 GMT
Last edited by Doug Newgard (Scimmia) - Wednesday, 21 September 2016, 04:02 GMT
|
Details
Description:
could not create ipvlan network by "docker network create -d ipvlan -o parent=ens33 ipvlan" docker daemon gives warning logs "Unable to locate plugin: ipvlan, retrying in 1s" Additional info: * package version(s) pacman -Qi docker Name : docker Version : 1:1.12.1-1 Description : Pack, ship and run any application as a lightweight container Architecture : x86_64 URL : https://www.docker.com/ Licenses : Apache Groups : None Provides : None Depends On : bridge-utils iproute2 device-mapper sqlite systemd libseccomp Optional Deps : btrfs-progs: btrfs backend support lxc: lxc backend support Required By : docker-compose Optional For : None Conflicts With : None Replaces : None Installed Size : 75.18 MiB Packager : Sébastien Luttringer <seblu@seblu.net> Build Date : Fri 19 Aug 2016 08:04:06 AM CST Install Date : Mon 12 Sep 2016 11:22:27 AM CST Install Reason : Explicitly installed Install Script : Yes Validated By : None * config and/or log files etc. Steps to reproduce: 1. modprobe ipvlan 2. lsmod |grep ipvlan 3. docker network create -d ipvlan -o parent=ens33 ipvlan GET ERROR "Error response from daemon: plugin not found" |
This task depends upon
Closed by Doug Newgard (Scimmia)
Wednesday, 21 September 2016, 04:02 GMT
Reason for closing: Not a bug
Wednesday, 21 September 2016, 04:02 GMT
Reason for closing: Not a bug
Comment by zml.xyz (zml.xyz) -
Monday, 12 September 2016, 09:37 GMT
it seems ipvlan network driver is still in experimental mode