"stage1: failed to setup network: failed to create ipvlan: operation not supported" - after update to 1298.5.0 #1843

Closed
f0 opened this Issue Mar 5, 2017 · 6 comments

Comments

Projects
None yet
5 participants
@f0

f0 commented Mar 5, 2017

after updating to 1298.5.0 i can no longer run container with ipvlan

/opt/bin/rkt --insecure-options=all run --net=default-restricted,vlan-2880:IP=10.62.0.110 aci.example.net/aci-base:3
stage1: failed to setup network: failed to create ipvlan: operation not supported

after rollback to 1235.9.0 , it does work without errors

i use rkt 1.25 with both

@f0 f0 changed the title from stage1: failed to setup network: failed to create ipvlan: operation not supported after update to 1298.5.0 to "stage1: failed to setup network: failed to create ipvlan: operation not supported" - after update to 1298.5.0 Mar 5, 2017

@lucab

This comment has been minimized.

Show comment
Hide comment
Member

lucab commented Mar 6, 2017

/cc @squeed

@squeed

This comment has been minimized.

Show comment
Hide comment
@squeed

squeed Mar 6, 2017

This is because CoreOS Container Linux is missing the NET_L3_MASTER_DEV kconfig (see the fedora bug). This dependency was added in kernel 4.9 in this commit.

So, we need to set NET_L3_MASTER_DEV=y and consider bringing this fix to the other channels.

squeed commented Mar 6, 2017

This is because CoreOS Container Linux is missing the NET_L3_MASTER_DEV kconfig (see the fedora bug). This dependency was added in kernel 4.9 in this commit.

So, we need to set NET_L3_MASTER_DEV=y and consider bringing this fix to the other channels.

@dm0-

This comment has been minimized.

Show comment
Hide comment
@dm0-

dm0- Mar 7, 2017

Member

This was auto-closed by the PR against master. I'm also pushing the fix to the beta and stable branches.

Member

dm0- commented Mar 7, 2017

This was auto-closed by the PR against master. I'm also pushing the fix to the beta and stable branches.

@f0

This comment has been minimized.

Show comment
Hide comment
@f0

f0 Mar 9, 2017

@dm0- big thx for fixing this, is there a known rollout date for stable?

f0 commented Mar 9, 2017

@dm0- big thx for fixing this, is there a known rollout date for stable?

@dm0-

This comment has been minimized.

Show comment
Hide comment
@dm0-

dm0- Mar 10, 2017

Member

@f0 Unless there are any critical security fixes before then, we should release a patched stable version on Wednesday of next week (and a new alpha is scheduled for Thursday).

Member

dm0- commented Mar 10, 2017

@f0 Unless there are any critical security fixes before then, we should release a patched stable version on Wednesday of next week (and a new alpha is scheduled for Thursday).

@f0

This comment has been minimized.

Show comment
Hide comment

f0 commented Mar 11, 2017

@dm0- ok thx

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment