Skip to content
This repository has been archived by the owner on May 12, 2021. It is now read-only.

add macvlan error -- kata-runtime 1.3.1 #853

Closed
coos opened this issue Oct 24, 2018 · 9 comments
Closed

add macvlan error -- kata-runtime 1.3.1 #853

coos opened this issue Oct 24, 2018 · 9 comments

Comments

@coos
Copy link

coos commented Oct 24, 2018

1、add some json in /etc/docker/daemon.json:

"runtimes": {
        "kata-runtime": {
            "path": "/opt/kata/bin/kata-runtime"
        }
    }

2、run containers:

root# /opt/kata/bin/kata-runtime --version
kata-runtime  : 1.3.1
   commit   : 258eae021387b7fffee48a120e6b5afdd7c78a00
   OCI specs: 1.0.1


root# docker network create -d macvlan --subnet=172.17.8.0/24 --gateway=172.17.8.254 -o parent=bond0.1008 vlan1008

root# docker run -d --net vlan1008 --ip 172.17.8.100 --runtime kata-runtime --storage-opt size=150G -m 4g --cpus=4 xxxxx/c7-systemd-kata

3416f232cf26aed4906644da0a3bb9afb054338aa64a3a844fd8f141fd08077d
docker: Error response from daemon: OCI runtime create failed: Could not get veth interface: eth0: Incorrect link type macvlan, expecting veth: unknown.
@jodh-intel
Copy link
Contributor

/cc @egernst, @mcastelino, @amshinde.

@mcastelino
Copy link
Contributor

@coos we are in the process of adding support for a different networking mode in Kata which uses port mirroring. Once that is merged in you should be able to use both macvlan and ipvlan.

The PR that is in progress is #827

@amshinde
Copy link
Member

@mcastelino We had added in an implementation based on macvtap earlier.
@jcvenegas I just verified that this works on master but not on release 1.3.1. Did this not go in 1.3.1?

@mcastelino
Copy link
Contributor

@amshinde the macvtap solution requires a modified CNI plugin right? The port mirroring option lets the use macvlan itself vs mactap?

@jcvenegas
Copy link
Member

@amshinde the only network related PR that was backported to 1.3.1 was d267da7

@egernst
Copy link
Member

egernst commented Nov 1, 2018

This should probably just be in 1.4, once it comes, since it is a feature more than a bug fix.

@amshinde
Copy link
Member

amshinde commented Nov 1, 2018

Yes I agree, this should go in 1.4.
@coos This will be available in our 1.4 release.

@coos
Copy link
Author

coos commented Nov 3, 2018

Thanks. When can I use 1.4 release?

@devimc
Copy link

devimc commented Dec 5, 2018

@coos

Thanks. When can I use 1.4 release?

it was released last week, please try it out it 😄

@coos coos closed this as completed Dec 11, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants