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

Releases: weaveworks/ignite

v0.10.0

19 Jul 20:54
4540abe
Compare
Choose a tag to compare

Released: 7/19/2021

This release adds two major features and a new API version.
VM annotations can be used to tell ignite another system will inject interfaces into the sandbox container's net-namespace.
These annotations will also tell ignite to plumb those sandbox interfaces to the firecracker MicroVM using tc_redirect. (code example)

kind: VM
apiVersion: ignite.weave.works/v1alpha4
metadata:
  annotations:
    ignite.weave.works/interface/eth0: 'dhcp-bridge'
    ignite.weave.works/interface/eth2: 'tc-redirect'
    ignite.weave.works/interface/eth3: 'tc-redirect'
    ignite.weave.works/interface/macvtap-uvnrt: 'macvtap'
    ignite.weave.works/interface/macvtap-hgfeq: 'macvtap'
    ignite.weave.works/sandbox-env/FIRECRACKER_GO_SDK_REQUEST_TIMEOUT_MILLISECONDS: "1000"
    ignite.weave.works/sandbox-env/FIRECRACKER_GO_SDK_INIT_TIMEOUT_SECONDS: "1"

It's now possible to use OS and kernel images from an authenticated private registry.
Interface bonding is also enabled in the newest ignite kernels.

New base OS images and kernels have been released with the GitHub Actions release tools.
The default kernel has been updated from 5.4.108 to 5.10.51.

This release consists of 12 noteworthy PR's from 4 contributors. 4 of these patches were sent by 2 external contributors.
Thanks so much for using and contributing back to the project.

Cheers to everyone who was part of shipping this release:

Installing

Check out the guide here: https://ignite.rtfd.io/en/stable/installation/

OCI Images for this release

ignite ( sandbox )

ignite-kernel:4.14.239 [multi-arch]
ignite-kernel:4.19.197 [multi-arch]
ignite-kernel:5.4.133 [multi-arch]
ignite-kernel:5.10.51 [multi-arch] ( default )
ignite-kernel:5.12.18 [multi-arch]
ignite-kernel:5.13.3 [multi-arch]

ignite-amazon-kernel
ignite-amazonlinux 2
ignite-alpine
ignite-centos 7, 8
ignite-opensuse tumbleweed, leap (⚠️ Build is broken! #859)
ignite-ubuntu [multi-arch] 16.04, 18.04, 20.04
ignite-kubeadm [multi-arch] v1.18.3
ignite-k3s v1.20.4


Features

Bug Fixes

  • Ignore not found error while deactivating snapshot (#823, darkowlzz)
  • SIGSEGV with metadata from older version of ignite (#854, juozasg)

Kernel

Docs

Dependencies

Automated

v0.9.0

12 Apr 16:58
e560f62
Compare
Choose a tag to compare

Released: 4/12/2021

This release allows changing the internal id prefixes of VM components. This overcomes limitations /w CNI's like Weave net.
A U/X improvement has been made to the VM list command to show when the container runtime state of the VM does not match what
ignite has stored in the API objet.

New base OS images and kernels have been released with the GitHub Actions release tools.
A k3s OS image is now pushed for amd64.
The default kernel has been updated to 5.4.108.

This release consists of 37 noteworthy PR's from 6 contributors. 11 of these patches were sent by 3 external contributors.
11 patches were sent by 3 people new to the project; welcome! :)
Thanks so much for using and contributing back to the project.

Cheers to everyone who was part of shipping this release:

Installing

Check out the guide here: https://ignite.rtfd.io/en/stable/installation/

OCI Images for this release

ignite ( sandbox )

ignite-kernel:4.14.227 [multi-arch]
ignite-kernel:4.19.183 [multi-arch]
ignite-kernel:5.4.108 [multi-arch] ( default )
ignite-kernel:5.10.25 [multi-arch]

ignite-amazon-kernel
ignite-amazonlinux 2
ignite-alpine
ignite-centos 7, 8
ignite-opensuse tumbleweed, leap
ignite-ubuntu [multi-arch] 16.04, 18.04, 20.04
ignite-kubeadm [multi-arch] v1.18.3
ignite-k3s v1.20.4


Enhancements

Runtime

  • Change the log level in RemoveContainer to debug (#812, darkowlzz)
  • runtime: Get containerd container task status (#779, darkowlzz)
  • Fix containerd cont delete when task load or delete fails (#791, stealthybox)
  • Avoid race between stop/kill and wait (#773, bboreham)

Bug Fixes

  • runtime: Handle error when container not found (#809, darkowlzz)
  • Handle error when the backend storage is uninitialized (#807, darkowlzz)
  • ps: Handle error when the backend storage is uninitialized (#778, darkowlzz)
  • Use declarative port mappings and copy files values when CLI flags are empty (#796, onatm)
  • Fix vm stop-start with default providers (#735, darkowlzz)
  • Avoid crash when network has no gateway (#749, bboreham)
  • Refactor: extract TarExtract function (#762, bboreham)

Docs

OS Images

Kernels

  • Support for Linux LTS kernel 5.10.x (#804, gaby)
  • Upgrade kernel versions (#798, gaby)
  • Bump default kernel to 5.4.102 (#806, gaby)
  • Bump Kernel versions. Bump default kernel version to 5.4.108 (#811, gaby)
  • Bump Kernel Versions for #811 (#815, stealthybox)

Dependencies

Build

Testing

Releasing

Automated

Read more

v0.8.0

09 Nov 20:53
77f6859
Compare
Choose a tag to compare

v0.8.0

Released: 11/9/2020

We're happy to share that ignite can now be generally configured with a central config file.
Check out the docs for how to configure ignite here.

Using this new config, it's no longer necessary to remember to pass --runtime and --network-plugin with every command.
You can choose your own default behavior.

Working with individual VM's is now also much less error-prone.
This release includes a new API version, v1alpha3, which allows VM's to remember their runtime and network config.

There's no current tooling for migrating to the new VM API for live workloads.
However, older API objects are forwards compatible, and restarting the workload should upgrade the API on disk.
As always, taking any necessary backups and re-creating workloads is the safest upgrade path :)

As is tradition, we have fixed bugs: networking bugs, lifecycle bugs, little UX things -- check the list.

It's now possible to run ignite within nested container environements such as containerd-within-docker and WSL2.
Detailed documentation for containerized setups will graduate from issue comments to the latest docs site soon.

It's really notable that our e2e test suite is getting more complete!
It's great to work with a project where confidence improves with every new patch, haha!

Alongside this release, we've updated all of the base OS images with new release tools powered by GitHub Actions.
We're not shipping any new kernels, so the default is the same as before -- new kernels will be pushed in an upcoming release.

This release consists of 52 noteworthy PR's from 10 contributors. 37 of these patches were sent by 6 external contributors.
7 patches were sent by 5 people new to the project; welcome! :)
Thanks so much for using and contributing back to the project.

Cheers to everyone who was part of shipping this release:

Installing

Check out the guide here: https://ignite.rtfd.io/en/stable/installation/

OCI Images for this release

ignite ( sandbox )

ignite-amazon-kernel
ignite-amazonlinux 2
ignite-alpine
ignite-centos 7, 8
ignite-opensuse tumbleweed, leap
ignite-ubuntu [multi-arch] 16.04, 18.04, 20.04
ignite-kubeadm [multi-arch] v1.18.3


Features

Enhancements

  • Update ignite help, image and kernel to no longer require root (#676, Khalian)
  • Build kernel from a specific git tag (#725, darkowlzz)
  • Shadow the bogus /etc/resolv.conf of centos:8 to fix wksctl (#611, twelho)
  • Make runtime and network-plugin VM create flags (#669, darkowlzz)
  • Fix in-container device nodes for containerd runtime (#653, stealthybox)
  • Exec blkid to getUUID() instead of relying on udevd symlinks (#652, stealthybox)
  • Configure dmsetup to fallback to managing device nodes without udevd (#654, stealthybox)

Documentation

Bug Fixes

API Changes

Cleanup

Testing

Release Infra

Read more

v0.7.1

13 Jul 16:11
e80a75a
Compare
Choose a tag to compare

The first patch release in the v0.7.X series pulls in an important fix for the long-standing networking issues in Ignite, with #638 merged you should be able to seamlessly integrate with different CNI providers and implement multi-node networking with Ignite VMs.

v0.7.1 also brings improvements to the GitOps functionality courtesy of @luxas
and link checking improvements by @dholbach. Thanks!

Next Steps / Installation

In short:

export VERSION=v0.7.1
export GOARCH=$(go env GOARCH 2>/dev/null || echo "amd64")

for binary in ignite ignited; do
    echo "Installing ${binary}..."
    curl -sfLo ${binary} https://github.com/weaveworks/ignite/releases/download/${VERSION}/${binary}-${GOARCH}
    chmod +x ${binary}
    sudo mv ${binary} /usr/local/bin
done

export CNI_VERSION=v0.8.5
export ARCH=$([ $(uname -m) = "x86_64" ] && echo amd64 || echo arm64)
sudo mkdir -p /opt/cni/bin
curl -sSL https://github.com/containernetworking/plugins/releases/download/${CNI_VERSION}/cni-plugins-linux-${ARCH}-${CNI_VERSION}.tgz | sudo tar -xz -C /opt/cni/bin

A more thorough installation guide is available here: https://ignite.readthedocs.io/en/latest/installation

OCI Images for this release

ignite (sandbox)

Enhancements

  • Shadow the bogus /etc/resolv.conf of centos:8 to fix wksctl (#611, @twelho)
  • Rename the gitops-toolkit dependency to libgitops (#612, @twelho)
  • Use the new knownhosts package in fluxcd/toolkit (#617, @luxas)
  • Use the new libgitops GitDirectory implementation (#615, @luxas)

Bug Fixes

  • Fix CNI networking issues (MAC duplication + bridge ageing) (#638, @twelho)

Documentation

v0.7.0

03 Jun 07:23
Compare
Choose a tag to compare

v0.7.0

Released: 02/06/2020

We're excited to cut a large release.
This release consists of 57 noteworthy PR's from 13 contributors. 27 of these patches were sent by 8 external contributors -- thanks so much for using and contributing back to the project!

Among some of the many patches, VM's can now be started in parallel. (Images should be pulled beforehand)
The ignite ssh and ignite exec commands now share a native go implementation.
We've added the ignite cp command along with improved CLI UX through filtering, templating, and examples.
You can now also create and run VM's imperatively using YAML files with the --config flags.

Performance and stability improvements in VM and network lifecycle should make using ignite more pleasant,
and the various bugfixes allow newer versions of Ubuntu to start functioning.

Lastly, we're announcing initial support for ARM devices.
Our docker images for ignite-kernels as well os our OS images for Ubuntu and kubeadm now ship with a manifest
list and {}-arm64 tag.
We've pushed a fresh set of kernel and OS images to dockerhub to support this.
Check out our new guide for ARM -- try it out on your ARM server or RaspberryPi and let us know how it works for you.

It was difficult to condense all of that!

As a special note, Sunny(@darkowlzz) from the @StorageOS team has joined ignite as a maintainer. Thanks for all of your help, Sunny!

Cheers to everyone who was part of shipping this release:

Next Steps / Installation

In short:

export VERSION=v0.7.0
export GOARCH=$(go env GOARCH 2>/dev/null || echo "amd64")

for binary in ignite ignited; do
    echo "Installing ${binary}..."
    curl -sfLo ${binary} https://github.com/weaveworks/ignite/releases/download/${VERSION}/${binary}-${GOARCH}
    chmod +x ${binary}
    sudo mv ${binary} /usr/local/bin
done

export CNI_VERSION=v0.8.5
export ARCH=$([ $(uname -m) = "x86_64" ] && echo amd64 || echo arm64)
sudo mkdir -p /opt/cni/bin
curl -sSL https://github.com/containernetworking/plugins/releases/download/${CNI_VERSION}/cni-plugins-linux-${ARCH}-${CNI_VERSION}.tgz | sudo tar -xz -C /opt/cni/bin

A more thorough installation guide is available here: https://ignite.readthedocs.io/en/latest/installation

OCI Images for this release

ignite ( sandbox )

ignite-kernel:4.14.182 [multi-arch]
ignite-kernel:4.19.125 [multi-arch] ( default )
ignite-kernel:5.4.43 [multi-arch]

ignite-amazon-kernel
ignite-amazonlinux 2
ignite-alpine
ignite-centos 7, 8
ignite-opensuse tumbleweed, leap
ignite-ubuntu [multi-arch] 16.04, 18.04, 20.04
ignite-kubeadm [multi-arch] v1.18.3


Enhancements

Kernel Improvements

Bug Fixes

Documentation

Read more

v0.6.3

10 Dec 07:16
Compare
Choose a tag to compare

v0.6.3

Released: 10/12/2019

This is the third patch release in the v0.6.x series, containing 1 security bug fix.

See #500 for ignite-specific details regarding this CVE.

Security Bug Fixes

Trying it out / Next Steps!

In short:

export VERSION=v0.6.3
export GOARCH=$(go env GOARCH 2>/dev/null || echo "amd64")

for binary in ignite ignited; do
    echo "Installing ${binary}..."
    curl -sfLo ${binary} https://github.com/weaveworks/ignite/releases/download/${VERSION}/${binary}-${GOARCH}
    chmod +x ${binary}
    sudo mv ${binary} /usr/local/bin
done

export CNI_VERSION=v0.8.2
export ARCH=$([ $(uname -m) = "x86_64" ] && echo amd64 || echo arm64)
mkdir -p /opt/cni/bin
curl -sSL https://github.com/containernetworking/plugins/releases/download/${CNI_VERSION}/cni-plugins-linux-${ARCH}-${CNI_VERSION}.tgz | tar -xz -C /opt/cni/bin

A more throughout installation guide is available here: https://ignite.readthedocs.io/en/latest/installation.html


OCI images for this release

v0.6.2

08 Oct 04:02
Compare
Choose a tag to compare

This is the second patch release in the v0.6.X series, containing bugfixes:
It moves the blocking SSH wait for vm's run with --ssh to using the actual protocol.
It also fixes a locale bug with resize2fs parsing that used to occur when using zh_CN.utf8.

Bug Fixes

Documentation

Trying it out / Next Steps!

In short:

export VERSION=v0.6.2
export GOARCH=$(go env GOARCH 2>/dev/null || echo "amd64")

for binary in ignite ignited; do
    echo "Installing ${binary}..."
    curl -sfLo ${binary} https://github.com/weaveworks/ignite/releases/download/${VERSION}/${binary}-${GOARCH}
    chmod +x ${binary}
    sudo mv ${binary} /usr/local/bin
done

A more throughout installation guide is available here: https://ignite.readthedocs.io/en/latest/installation.html


OCI images for this release

v0.5.5

08 Oct 03:43
Compare
Choose a tag to compare

This is the fifth patch release in the v0.5.X series, containing bugfixes:
It moves the blocking SSH wait for vm's run with --ssh to using the actual protocol.
It also fixes a locale bug with resize2fs parsing that used to occur when using zh_CN.utf8.

Bug Fixes

Documentation

Trying it out / Next Steps!

In short:

export VERSION=v0.5.5
export GOARCH=$(go env GOARCH 2>/dev/null || echo "amd64")

for binary in ignite ignited; do
    echo "Installing ${binary}..."
    curl -sfLo ${binary} https://github.com/weaveworks/ignite/releases/download/${VERSION}/${binary}-${GOARCH}
    chmod +x ${binary}
    sudo mv ${binary} /usr/local/bin
done

A more throughout installation guide is available here: https://ignite.readthedocs.io/en/latest/installation.html


OCI images for this release

v0.6.1

02 Oct 23:24
Compare
Choose a tag to compare

We're excited to release v0.6.1 with usability improvements and lots of bug fixes :)

This release consists of 32 noteworthy PRs from 6 contributors over the past month.
We had 7 contributions from 4 external contributors. Thanks so much!

Ignite should now work with most installations of containerd -- even those that are installed underneath upstream docker.
Care has been taken with our installation instructions to ensure we are not breaking users docker installations.
We've also implemented a graceful fallback to older containerd-shim versions and now support containerd-shim-runc-v2.

This release also contains numerous fixes that make the CNI network plugin work much more reliably.
Connections to the internet from vm's using CNI should now work on most machines by default.
Please see the following user-facing change.

Default CNI Network Change

The default cni0 bridge has changed to a new ignite0 bridge introduced by the #460 bugfix. This comes with a new subnet as well.
We did this because the default CNI config shipped in v0.6.0 was a non-working configuration for most users.
You may continue to use the default CNI configuration. Nothing will change automatically.

If you are using your own CNI configuration, this does not affect you.

To migrate your running CNI networked vm's to the new default subnet, you can:

  1. install this new ignite version
  2. stop the relevant vm's
  3. delete the CNI network
  4. restart them

Example:

# first, upgrade to ignite v0.6.1

# list all vm's on the default 172.18.0.0/16 CNI network
sudo bin/ignite vm ls | grep '\b172.18.[0-9][0-9]*.[0-9][0-9]*\b'
# stop the listed vm's with the appropriate runtime
sudo bin/ignite stop my-containerd-vm
sudo bin/ignite stop my-docker-vm --runtime docker

# remove the old CNI network config
sudo rm -rf rm /etc/cni/net.d/
# optional: remove the old bridge
sudo ifconfig cni0 down
sudo ip link delete cni0

# restart your vm's
sudo bin/ignite start my-containerd-vm
sudo bin/ignite start my-docker-vm --runtime docker
# Your vm's will now have addresses configured in the 10.61.0.0/16 subnet.
# If they did not have internet connectivity before, they now should.

Enhancements

Bug Fixes

  • Change default CNI network name, bridge name, and subnet #460, @stealthybox
  • Chain firewall plugin to fix routing for default CNI bridge #442, @stealthybox
  • Teardown IPMasq rules for all actual configured bridges instead of using the hardcoded default string (#461, @stealthybox)
  • Fix containerd resolv.conf + DHCP behavior (#441, @stealthybox)
  • Make getIPChains more precise and less failure-prone (#426, @stealthybox)
  • quick fix typo umount as unmount in preflight check (#415, @chanwit)
  • fix possible dm snapshot leaks (#381, @chanwit)
  • make rm command more robust with addition check (#413, @chanwit)

Documentation

Dependencies

Development

Governance

Trying it out / Next Steps!

In short:

export VERSION=v0.6.1
export GOARCH=$(go env GOARCH 2>/dev/null || echo "amd64")

for binary in ignite ignited; do
    echo "Installing ${binary}..."
    curl -sfLo ${binary} https://github.com/weaveworks/ignite/releases/download/${VERSION}/${binary}-${GOARCH}
    chmod +x ${binary}
    sudo mv ${binary} /usr/local/bin
done

A more throughout installation guide is available here: https://ignite.readthedocs.io/en/latest/installation.html


OCI images for this release

v0.5.4

24 Sep 05:26
Compare
Choose a tag to compare

This is the fourth patch release in the v0.5.X series, containing one enhancement that implements the blocking SSH wait for vm's run with --ssh.

Enhancements

Release Machinery

  • 0.5.x -- On release, use tidy-in-docker to prevent module differences from differing versions of go (#434, @stealthybox)

Trying it out / Next Steps!

In short:

export VERSION=v0.5.4
export GOARCH=$(go env GOARCH 2>/dev/null || echo "amd64")

for binary in ignite ignited; do
    echo "Installing ${binary}..."
    curl -sfLo ${binary} https://github.com/weaveworks/ignite/releases/download/${VERSION}/${binary}-${GOARCH}
    chmod +x ${binary}
    sudo mv ${binary} /usr/local/bin
done

A more throughout installation guide is available here: https://ignite.readthedocs.io/en/latest/installation.html


OCI images for this release