English
« Back to projectatomic.io
Ask Your Question
0

Has someone tried the macvlan network driver?

asked 2016-11-09 17:31:05 +0000

bla-kw gravatar image

updated 2016-11-11 10:33:35 +0000

I tried docker-latest (1.12.1) with the current CentOS atomic release (7.20161104) and wanted to test the macvlan network driver ( https://docs.docker.com/engine/usergu... ).

I can create the network and connect containers to it:

docker network create -d macvlan --subnet="191.168.1.0/24" --gateway="192.168.1.1" -o parent=eth0 test
docker run --net=test --ip="192.168.1.10" -it --rm alpine /bin/sh

Containers in this network can communicate with each other, but from the container I can not reach the external gateway and also from an external host in 192.168.1.0/24 I can not reach the container.

On other distributions I got macvlan network to work. I don't see what the problem in atomic is. The macvlan kernel module is loaded, the Linux kernel is greater than v3.9.Docker is v1.12.0+. setenforce 0 does not change anything.

edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted
0

answered 2017-02-03 15:47:58 +0000

I was able, a few days ago, to find an OVirt mailing list message that mentioned what appears to be the same issue. In that specific case, the user was able to "resolve" the issue by using the mainline Linux kernel, rather than the CentOS (Fedora?) one. Hopefully a kernel update will eventually resolve this.

edit flag offensive delete link more

Comments

Here's the link to what I was talking about: http://www.spinics.net/lists/netdev/msg296963.html Looks like it only applies to Bond interfaces, though.

mossholderm ( 2017-02-06 15:49:20 +0000 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

[hide preview]

Question Tools

Follow
1 follower

Stats

Asked: 2016-11-09 17:31:05 +0000

Seen: 512 times

Last updated: Feb 03