Skip to content

Aleph-vm 1.0.1

Compare
Choose a tag to compare
@nesitor nesitor released this 27 Aug 15:37
· 35 commits to main since this release
d66de42

This release fixes an important bug for confidentials computing.

Main changes

Core Functionality and Stability

  • Bug Fixes: Addressed issue running a confidential VM inside an updated CRN.

What's Changed

  • Update aleph_message package on packaging steps by @nesitor in #684

Full Changelog: 1.0.0...1.0.1

How to upgrade

1. Upgrade the packages

This part did not change, download and install the new package as usual.

On Debian 11 (Bullseye):

rm -f /opt/aleph-vm.debian-11.deb
wget -P /opt https://github.com/aleph-im/aleph-vm/releases/download/1.0.1/aleph-vm.debian-11.deb
apt install /opt/aleph-vm.debian-11.deb

On Debian 12 (Bookworm):

rm -f /opt/aleph-vm.debian-12.deb
wget -P /opt https://github.com/aleph-im/aleph-vm/releases/download/1.0.1/aleph-vm.debian-12.deb
apt install /opt/aleph-vm.debian-12.deb

On Ubuntu 22.04 (Jammy Jellyfish):

rm -f /opt/aleph-vm.ubuntu-22.04.deb
sudo wget -P /opt https://github.com/aleph-im/aleph-vm/releases/download/1.0.1/aleph-vm.ubuntu-22.04.deb
sudo apt install /opt/aleph-vm.ubuntu-22.04.deb

On Ubuntu 24.04 (Noble Numbat):

rm -f /opt/aleph-vm.ubuntu-24.04.deb
sudo wget -P /opt https://github.com/aleph-im/aleph-vm/releases/download/1.0.1/aleph-vm.ubuntu-24.04.deb
sudo apt install /opt/aleph-vm.ubuntu-24.04.deb

2. Enable Confidential Computing (optional)

In order to enable Confidential Computing on our Compute Resource Node, you must:

  1. Use an AMD CPU from the 8004 or 9004 families.
  2. Ensure that your system supports confidential computing. We have only tested Ubuntu 24.05 so far.
  3. Enable SEV and SEV-SNP in the BIOS.
  4. Enable confidential computing in the aleph-vm configuration.

Enable SEV in the configuration of aleph-vm, by default in /etc/aleph-vm/supervisor.env. This is not the default yet.

ALEPH_VM_ENABLE_CONFIDENTIAL_COMPUTING=True

After launching the server you can check the endpoint
http://localhost:4020/status/config or https://<your-node-domain>/status/config and verify that ENABLE_CONFIDENTIAL_COMPUTING has the value true.