ignite
ignite copied to clipboard
failed to setup network for namespace
Have the same error again and again even on different operating systems. In my case it was Alpinelinux, Debian and Ubuntu where this error occurs after a fresh installation.
Here demonstrated on an Alpinelinux system
localhost:~# ignite run weaveworks/ignite-ubuntu
INFO[0001] Created VM with ID "dc3e8c99f785c567" and name "cold-dust"
INFO[0001] Networking is handled by "cni"
INFO[0001] Started Firecracker VM "dc3e8c99f785c567" in a container with ID "ignite-dc3e8c99f785c567"
localhost:~# ignite ssh dc3
FATA[0000] VM "dc3e8c99f785c567" is not running
localhost:~# ignite start -i dc3
ERRO[0000] failed to setup network for namespace "ignite-dc3e8c99f785c567": failed to allocate for range 0: 10.61.0.6 has been allocated to ignite-dc3e8c99f785c567, duplicate allocation is not allowed
FATA[0000] failed to allocate for range 0: 10.61.0.6 has been allocated to ignite-dc3e8c99f785c567, duplicate allocation is not allowed
Ignite Version
Ignite version: version.Info{Major:"0", Minor:"6", GitVersion:"v0.6.3", GitCommit:"ed51b9378f6e0982461074734beb145d571d56a6", GitTreeState:"clean", BuildDate:"2019-12-10T06:19:57Z", GoVersion:"go1.12.10", Compiler:"gc", Platform:"linux/amd64"}
Firecracker version: v0.18.1
Runtime: containerd
Thank you for reporting. It seems you have a subnet with 10.61.0.0/x on the machine?
maybe ip addr
could tell us more about this?
Hello, first of all thanks for the quick answer.
Here is the Result:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
link/ether 00:16:3c:4f:50:67 brd ff:ff:ff:ff:ff:ff
inet xxx.xxx.xxx.xxx/16 scope global eth0
valid_lft forever preferred_lft forever
inet6 xxxx::xxx:xxxx:xxxx:xxxx/64 scope link
valid_lft forever preferred_lft forever
3: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN
link/ether 02:42:2a:a5:10:f1 brd ff:ff:ff:ff:ff:ff
inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0
valid_lft forever preferred_lft forever
4: ignite0: <BROADCAST,MULTICAST,UP,LOWER_UP100> mtu 1500 qdisc noqueue state UP qlen 1000
link/ether a2:3b:b3:66:bd:31 brd ff:ff:ff:ff:ff:ff
inet 10.61.0.1/16 brd 10.61.255.255 scope global ignite0
valid_lft forever preferred_lft forever
inet6 fe80::a03b:b3ff:fe66:bd31/64 scope link
valid_lft forever preferred_lft forever
6: veth4b1dd68d@docker0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master ignite0 state UP
link/ether 8e:51:c2:aa:97:80 brd ff:ff:ff:ff:ff:ff
inet6 fe80::8c51:c2ff:feaa:9780/64 scope link
valid_lft forever preferred_lft forever
I have the same problem under Debian, is there already a solution?
@chanwit Do you have any idea how to fix it?
Hello, does anyone have a solution to this problem?
Could you show us the exact step to reproduce this issue?