Skip to content
This repository has been archived by the owner on Aug 29, 2023. It is now read-only.

update to latest ignite #83

Merged
merged 1 commit into from
Jun 3, 2020
Merged

update to latest ignite #83

merged 1 commit into from
Jun 3, 2020

Conversation

dholbach
Copy link
Contributor

@dholbach dholbach commented Jun 3, 2020

@dholbach dholbach changed the title update to latest footloose and ignite update to latest ignite Jun 3, 2020
@chanwit
Copy link
Member

chanwit commented Jun 3, 2020

LGTM

@chanwit chanwit merged commit 35b30f9 into weaveworks:master Jun 3, 2020
@dholbach dholbach deleted the update-ignite branch June 3, 2020 15:20
@stealthybox
Copy link
Contributor

@dholbach @chanwit This updates the default backend from docker to containerd+CNI.
I don't believe firekube currently installs CNI for you.

@dholbach
Copy link
Contributor Author

dholbach commented Jun 5, 2020

After I've ran ./setup.sh from current master, I see this up and running:

daemonset.apps/weave-net

So I really think we're good.

@stealthybox
Copy link
Contributor

After I've ran ./setup.sh from current master, I see this up and running:

daemonset.apps/weave-net

This is unrelated to the CNI installed within the cluster.

Ignite v0.5.x uses docker and docker's networking to setup the MicroVM's.
In ignite v0.6.x and v0.7.x, the default behavior is changed to use Containerd and CNI for setting up the VM's.

Firekube's installation scripts install many components for the user.
Since CNI is now a dependency for starting ignite VM's, the setup.sh needs to install CNI plugins on Linux hosts.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants