Docs

Elastic Compute Service

veLinux images

Description of differences between veLinux 2.0 and veLinux 1.0

This topic describes the main differences between veLinux 2.0 image and veLinux 1.0 image.

Python

Supported versions

Since the core team of the Python upstream community discontinued support for Python 2 in January 2020, veLinux 2.0 no longer supports Python 2 and only supports Python 3.

Python interpreter

To follow the PEP-668 (Python Enhancement Proposal), in veLinux 2.0:

The Python 3 interpreter packages (PyPy 3 and Python 3.11) are marked as externally managed (external management).

Pip (python3-pip), the package manager for Python 3, blocks manual package installations in the Python 3 interpreter of veLinux 2.

tip

To manually install packages for the Python 3 interpreter, use the --break-system-packages option in the installation command.

If the Python application (or version) you need to install does not have a Deb package, we recommend that you install it with pipx.

If the Python library module (or version) you need to install does not have a Deb package, we recommend that you install it in a virtual environment (Virtualenv).

iptables

iptables is used for packet filtering, network address translation (NAT), and other packet management. Due to limits that can not be easily resolved, iptables is gradually replaced by nftables and no longer installed in veLinux 2.0 by default.

systemd

In veLinux 2.0, systemd (system initialization manager) uses the feature of cgroup v2 control group by default.

DKMS 3.0

In veLinux 2.0, the REMAKE_INITRD attribute is deleted from DKMS (Dynamic Kernel Module Support) 3.0. Therefore, after installing a new kernel, or installing/updating drivers, you need to manually execute the update-initramfs -u command to update the initial RAM file system (initramfs).

Rsyslog

In veLinux 2.0, Rsyslog (Remote System Logging) is of a lower priority and is not installed by default.

warning

If you decide to continue using Rsyslog:

The default high-precision timestamps (microsecond level) in Rsyslog may affect tools that analyze system logs. Therefore, you may need to update the rules for matching message creation time in your locally created Logcheck rules to ensure compatibility with the new Rsyslog format.

By default, Rsyslog no longer creates certain log files in /var/log. Messages that were originally written to these files will be written to the /var/log/syslog file.

Log files that are no longer created by Rsyslog include:

/var/log/mail.{info,warn,err}: These files contain messages from the local mail transfer agent (MTA).

/var/log/lpr.log: These files contain log messages related to printing.

/var/log/{messages,debug,daemon.log}: These files contain different types of system events and messages.

GRUB

Traditionally, GRUB has used os-prober by default to detect other operating systems installed on the computer and add them to the boot menu. However, this operation may cause issues such as boot delays, cluttered boot menus, and incorrect booting. Therefore, veLinux 2.0 no longer uses os-prober for GRUB by default.

tip

If you need to use GRUB to boot the system in veLinux 2.0 and to have other operating systems displayed in the boot menu, execute the dpkg-reconfigure <GRUB package name> command to change the GRUB configuration.

Key management method

To improve system security and manageability, veLinux 2.0 no longer recommends the usage of apt-key to manage the key. If you continue to use apt-key, you will receive warning messages.

We recommend that you manage keys in the form of apt-key key files (.gpg or .asc) in the /etc/apt/trusted.gpg.d directory. For more details, refer to APT-KEY.

System identifier

In the veLinux 2.0 image, the /etc/os-release file has been updated to include veLinux system identifiers. You can use the lsb_release tool to display information about the veLinux system.

Last updated: 2026.06.18 17:48:25