Fl
Operating Systems Azure

Fedora Linux 45 Minimal on Azure User Guide

| Product: Fedora Linux 45 Minimal on Azure

Overview

This guide covers the deployment and configuration of Fedora Linux 45 Minimal on Microsoft Azure using cloudimg's pre configured virtual machine image from the Azure Marketplace.

Fedora Linux is the community distribution produced by the Fedora Project and sponsored by Red Hat, and it is where a great deal of enterprise Linux technology appears first. This image starts from the Fedora Project's own official Azure image and, in the same build, applies the three fixes cloudimg makes to its standard Fedora images: automatic security updates armed, the zram swap device removed and the LLMNR listener closed. In this guide, "the standard image" means the standard Fedora Linux 45 Cloud Edition image with those three fixes applied, and every figure below is measured against it. What makes this image different from the standard image is the package profile.

Fedora publishes no "minimal" environment for cloud images, but it does define its smallest package set: the core group in Fedora's own package metadata, which Fedora describes as the "Smallest possible installation". This image keeps the mandatory packages of that group, the Azure provisioning, boot and security stack, and their dependencies, and removes everything else. The result, measured on this image against the standard image:

  • 367 installed packages instead of 462 (95 fewer)
  • 315 MiB less installed software (rpm payload 820 MiB instead of 1135 MiB)

Being straightforward about where that comes from: the largest single removal, dnf5 remove aardvark-dns, takes 43 packages and 255 MiB on its own: the container stack Fedora Cloud Edition ships, which is podman with its networking (netavark, aardvark-dns, passt), its runtimes (crun, conmon, criu), nftables and eighteen qemu-user-static emulators that arrive as weak dependencies. The rest is 52 packages and 60 MiB: the kmscon graphical console and its fonts, the older DNF 4 Python stack that only the tracer plugin used, the console login helper messages, rsync, the Unbound DNSSEC libraries, gawk's extra language packs, the minimal glibc language pack (the English one stays), prefixdevname, the systemd-oomd defaults, the PCI ID database and the libraries only they used. If that one removal is all you wanted, you could run it yourself on the standard image; this image goes the rest of the way to Fedora's own core definition and proves it.

The image describes itself: a manifest generated from its own package database ships at /usr/share/cloudimg/fedora-45-minimal.manifest, with the measured numbers and a trim ledger alongside it. Anything you miss is one dnf install away from Fedora's own repositories.

What's included:

  • Fedora Linux 45 Cloud Edition with the Minimal package profile: 367 packages, cut to Fedora's core group plus the Azure provisioning stack
  • Built from the Fedora Project's own official Azure disk image, checked against Fedora's GPG signed checksum file
  • The full Azure provisioning path, protected from the trim by construction: cloud-init, the Azure Linux Agent (waagent), azure-vm-utils, the Hyper-V daemons, OpenSSH, NetworkManager and the kernel and boot chain
  • A shipped manifest and trim ledger derived from the image's own package database
  • Every available update applied at build time and again immediately before capture
  • Automatic security updates installed, armed and enabled
  • Chrony for time synchronisation against the Azure host clock
  • SELinux in enforcing mode, the Fedora default
  • SSH as the only network listener, with no swap on the operating system disk
  • Gen2 Hyper V virtual machine support
  • cloudimg's support team on hand 24 hours a day by email (support@cloudimg.co.uk), with a guaranteed response within 24 hours

What's deliberately NOT included (each is one dnf install away): podman and the rest of the container stack, the qemu user mode emulators, nftables, rsync, the kmscon graphical console and its fonts, and the DNF 4 Python bindings. lvm2, mdadm, tpm2-tss and unzip all remain, because something in Fedora's core set or the Azure stack depends on them.

Platform: Microsoft Azure (Gen2 Hyper V, x64) Default user: azureuser

Read this first: Fedora's support window is about 13 months

Fedora Linux is a fast moving distribution, and that is the point of it — recent kernels, recent compilers, recent runtimes. It is not a long term support distribution, and this listing does not pretend otherwise.

Fedora Linux 45 was released on 3 November 2026 and reaches end of life on 8 December 2027. That date comes from the Fedora Project's own release system, Bodhi, which records Fedora 45 with eol: 2027-12-08, and endoflife.date agrees. After that date there are no further updates of any kind, including security updates.

  1. Plan the upgrade to Fedora 46 before December 2027. Fedora is upgraded in place; the procedure is in Step 10 below.
  2. If you need a multi year support window, this is the wrong image. cloudimg publishes AlmaLinux, Rocky Linux and Oracle Linux Minimal images with ten year enterprise lifecycles, and those are the right choice for a long lived production fleet.

The image's own /etc/os-release carries a SUPPORT_END value set by Fedora's release package, 2027-12-08 on this image, which agrees with Bodhi. If the two ever disagree, Bodhi is the authoritative source.

This is Fedora Cloud Edition

The base is Fedora Cloud Edition, the headless, server ready edition Fedora publishes for cloud platforms. It is not Fedora Server Edition, and this listing does not call itself "Fedora Server" for that reason.

The Fedora Project publishes no official Fedora image to the Azure Marketplace, and every other Fedora offer there comes from a third party repackager. This image is built from the Fedora Project's own official Azure disk image, Fedora-Cloud-Base-Azure-45-1.4.x86_64.vhdfixed.xz, downloaded from dl.fedoraproject.org, with its SHA-256 verified against Fedora's published, GPG signed checksum file. It carries no Marketplace purchase plan of its own.

What this image changes

Everything below was measured before it was changed, and every change is reversible.

Compared with the stock Fedora Cloud Base image, this build first applies cloudimg's three fixes, which together make the standard image:

  • Automatic security updates are installed and armed. The stock image has no automatic update mechanism. This image installs dnf5-plugin-automatic, configures it in /etc/dnf/automatic.conf to apply security updates daily and never to reboot on its own, and enables its timer.
  • The zram swap device is removed. Azure image certification requires a Marketplace image to ship with no swap on the operating system disk, so this image ships an empty /etc/systemd/zram-generator.conf with the zram setup unit masked, and no zram device is created. Step 3 shows how to put it back.
  • LLMNR is switched off. The stock image's systemd-resolved listens for Link Local Multicast Name Resolution on port 5355 from off the machine; LLMNR is a well known spoofing vector and useless on a cloud server. A drop in file, /etc/systemd/resolved.conf.d/90-cloudimg-hardening.conf, turns it off, so SSH on port 22 is the only network listener.

It also hardens SSH with a drop in file that sorts ahead of every other SSH configuration file.

Compared with the standard image:

  • 95 packages are removed, by a guarded transaction: rpm's own dependency check and DNF's solver must both agree on the exact removal set, a trial transaction that includes systemd must be refused, and the build stops if the result is not measurably smaller than the standard image. Step 4 shows how to check the result yourself.

Security posture

This image ships with no known credential. There is no default password and no baked in SSH key:

  • The root account password is locked, and no account on the image has a usable password.
  • SSH accepts the sign in method you chose when you created the machine: your SSH key, or the password you set in the portal. Nothing in the image overrides that choice. Keyboard interactive authentication and empty passwords are disabled.
  • PermitRootLogin is prohibit-password, so root can never log in with a password. Use sudo from your admin user.
  • SSH host keys and /etc/machine-id are removed before capture and regenerated on each machine at first boot, so no two machines share a host identity.
  • The build account is deleted before capture, and the image is checked to confirm no account with a user ID of 1000 or above survives.
  • SELinux is left in enforcing mode and pinned enforcing for the next boot.
  • The trim itself is a security property: 95 fewer installed packages are 95 fewer things to carry vulnerabilities, patch and audit.

Prerequisites

  1. An active Microsoft Azure subscription
  2. Access to the Azure Portal or Azure CLI
  3. An SSH key pair for Linux VM access
  4. Familiarity with Azure VM management

Recommended VM Size: Standard_B2s (2 vCPU, 4 GB RAM) or larger.

Step 1: Deploy the Virtual Machine

Option A: Azure Portal

  1. Navigate to the Azure Marketplace and search for "Fedora Linux 45 Minimal cloudimg"
  2. Select the image and click Create
  3. Choose your subscription, resource group and region
  4. Pick a size such as Standard_B2s
  5. Set the administrator username and paste your SSH public key
  6. Allow inbound port 22 (SSH) and create the machine

Option B: Azure CLI

Run this on your own workstation, substituting your resource group, VM name and preferred region. Accept the Marketplace terms once per subscription, then create the machine:

az vm image terms accept --urn cloudimg1647283583153:fedora-45-minimal:default:latest

az vm create \
  --resource-group myResourceGroup \
  --name my-fedora-45-minimal-vm \
  --image cloudimg1647283583153:fedora-45-minimal:default:latest \
  --size Standard_B2s \
  --admin-username azureuser \
  --generate-ssh-keys \
  --public-ip-sku Standard

Step 2: Connect via SSH

ssh azureuser@<your-vm-public-ip>

Use the admin username you chose. If you created the machine with an SSH key, that key is accepted; if you chose a password in the portal, that password is accepted. Root cannot log in over SSH with a password.

Step 3: Confirm the release, the kernel and the disk

cat /etc/os-release
NAME="Fedora Linux"
VERSION="45 (Cloud Edition)"
RELEASE_TYPE=stable
ID=fedora
VERSION_ID=45
VERSION_CODENAME=""
PRETTY_NAME="Fedora Linux 45 (Cloud Edition)"
ANSI_COLOR="0;38;2;60;110;180"
LOGO=fedora-logo-icon
CPE_NAME="cpe:/o:fedoraproject:fedora:45"
HOME_URL="https://fedoraproject.org/"
DOCUMENTATION_URL="https://docs.fedoraproject.org/en-US/fedora/f45/"
SUPPORT_URL="https://ask.fedoraproject.org/"
BUG_REPORT_URL="https://bugzilla.redhat.com/"
REDHAT_BUGZILLA_PRODUCT="Fedora"
REDHAT_BUGZILLA_PRODUCT_VERSION=45
REDHAT_SUPPORT_PRODUCT="Fedora"
REDHAT_SUPPORT_PRODUCT_VERSION=45
SUPPORT_END=2027-12-08
VARIANT="Cloud Edition"
VARIANT_ID=cloud

The kernel is a packaged, managed kernel, and superseded kernels are removed before capture, so exactly one is installed:

uname -r && rpm -q kernel-core
7.3.4-300.fc45.x86_64
kernel-core-7.3.4-300.fc45.x86_64

Fedora Linux 45 Minimal release, kernel and disk layout

The disk layout

The image uses a flat GPT layout with no LVM: a small BIOS boot partition, an EFI system partition and a btrfs root partition carrying Fedora's standard subvolumes:

lsblk -o NAME,SIZE,FSTYPE,MOUNTPOINT && findmnt -no SOURCE,FSTYPE /
NAME    SIZE FSTYPE MOUNTPOINT
sda      30G
├─sda1    2M
├─sda2  100M vfat   /boot/efi
└─sda3 29.9G btrfs  /var
sdb       8G
└─sdb1    8G ext4   /mnt
sr0     630K
/dev/sda3[/root] btrfs

findmnt is the authoritative answer for /: the root filesystem is the btrfs root subvolume. lsblk prints only one of the several subvolumes mounted from sda3, and which one it picks is arbitrary. sr0 is the virtual CD-ROM Azure uses to pass provisioning data in.

sdb is the local resource disk that Standard_B2s provides, mounted at /mnt. It is ephemeral: its contents are lost whenever the machine is stopped and deallocated or moved to another host. Use it for scratch data only. Sizes without a local disk have no sdb.

sudo btrfs subvolume list /
ID 256 gen 142 top level 5 path root
ID 257 gen 62 top level 5 path boot
ID 258 gen 142 top level 5 path home
ID 259 gen 142 top level 5 path var

The gen numbers are btrfs generation counters and will differ on your machine; the four subvolume names are what matter.

The operating system disk is 30 GB and carries no swap:

df -hT / /boot/efi && swapon --show
Filesystem     Type   Size  Used Avail Use% Mounted on
/dev/sda3      btrfs   30G  661M   29G   3% /
/dev/sda2      vfat   100M   22M   79M  22% /boot/efi

swapon --show prints nothing, which means no swap is configured. If a workload wants Fedora's zram swap back:

sudo dnf install zram-generator
printf '[zram0]\nzram-size = ram / 2\n' | sudo tee /etc/systemd/zram-generator.conf
sudo systemctl unmask systemd-zram-setup@zram0.service
sudo systemctl daemon-reload
sudo systemctl start dev-zram0.swap

Step 4: Check the Minimal package profile

Count the installed packages. gpg-pubkey entries are the imported Fedora signing keys rather than software, so they are left out of the count:

rpm -qa | grep -vc '^gpg-pubkey'
367

The image carries a manifest generated from its own package database. Its header records the contract and the measured delta against the standard image:

grep '^#' /usr/share/cloudimg/fedora-45-minimal.manifest
# Fedora Linux 45 Minimal - cloudimg shipped manifest
# DERIVED from the rpm database of this image at capture, 2026-11-17T14:51:42Z - never hand-written.
# Contract: Fedora's own @core comps group ('Smallest possible installation', mandatory
# packages) + the Azure provisioning/boot/security lineage + their dependencies.
# Measured against the standard Fedora Linux 45 Cloud Edition image with cloudimg's three fixes: 462 -> 367 packages (-95), rpm payload -315 MiB.
# Largest single removal on that standard image ('dnf5 remove aardvark-dns'): -43 packages / -255 MiB.
# Installed now: 367 packages.
#
# --- capability notes, each DERIVED from the rpm database of this image ---
# CONTAINERS: no podman/container runtime (the standard Fedora Cloud image ships one). Restore: sudo dnf install podman
# LVM: lvm2 is installed.
# RAID: mdadm is installed.
# NFTABLES: no nftables CLI (the Azure agent's firewall uses iptables-legacy, which is kept). Restore: sudo dnf install nftables
# RSYNC: no rsync. Restore: sudo dnf install rsync
# PROVISIONING: cloud-init + WALinuxAgent + azure-vm-utils + hyperv-daemons installed - the full Azure path is retained.
# UPDATES: dnf5-plugin-automatic installed - security updates auto-apply (cloudimg's fix 1).
#
# name  epoch:version-release.arch

Below the header, every installed package is listed with its exact version, and the image's build gate checks that list against the package database in both directions. The full list of the 95 removed packages is in the trim ledger, /usr/share/cloudimg/fedora-45-minimal-trim.json.

Confirm that the best known of them are not installed here:

rpm -q podman qemu-user-static rsync nftables; echo "exit code: $?"
package podman is not installed
package qemu-user-static is not installed
package rsync is not installed
package nftables is not installed
exit code: 4

rpm -q exits with the number of packages it did not find, so 4 means none of the four is installed.

The trim leaves nothing orphaned, so your first dnf autoremove has nothing to take:

sudo dnf autoremove --assumeno
Nothing to do.

And the definition the image was cut to is Fedora's own, readable from the package metadata:

dnf -q group info core
Id                   : core
Name                 : Core
Description          : Smallest possible installation
Installed            : yes
Order                :
Langonly             :
Uservisible          : no
Repositories         : @System
Mandatory packages   : audit
                     : bash
                     : coreutils
                     : curl
                     : dnf5
                     : e2fsprogs
                     : filesystem
                     : glibc
                     : hostname
                     : iproute
                     : iputils
                     : kbd
                     : less
                     : man-db
                     : ncurses
                     : openssh-clients
                     : openssh-server
                     : parted
                     : policycoreutils
                     : procps-ng
                     : rootfiles
                     : rpm
                     : selinux-policy-targeted
                     : setup
                     : shadow-utils
                     : sssd-common
                     : sssd-kcm
                     : sudo
                     : systemd
                     : util-linux
                     : vim-minimal
Default packages     : NetworkManager
                     : dnf5-plugins
                     : dracut-config-rescue
                     : firewalld
                     : fwupd
                     : kmscon
                     : plymouth
                     : prefixdevname
                     : systemd-resolved
                     : zram-generator-defaults
Optional packages    : dracut-config-generic
                     : initial-setup
                     : initscripts

All 31 mandatory packages are installed. Of the group's default packages, NetworkManager, dnf5-plugins and systemd-resolved are installed; prefixdevname is removed here, zram-generator-defaults is removed by cloudimg's no-swap fix, and dracut-config-rescue, firewalld, fwupd and plymouth are not part of Fedora's own Azure image in the first place.

To put anything back, install it by name. For example, the container runtime:

sudo dnf install podman

The Minimal package profile measured from the image's own package database: the package count, the manifest's measured delta, the largest removals absent and the Azure stack present

Step 5: Check the patch level and automatic updates

Fedora 45 uses DNF 5. The dnf command is dnf5; almost every familiar command works unchanged. The image was fully updated immediately before capture:

sudo dnf check-update; echo "exit code: $?"
Updating and loading repositories:
Last metadata expiration check: 0:00:24 ago on 2026-11-17 15:16:39.
Repositories loaded.
exit code: 0

dnf check-update exits 0 when nothing is pending and 100 when updates are available. The first run on a new machine also downloads the repository metadata, so you will see progress lines above Repositories loaded.

Your update path is Fedora's own repositories, with GPG checking enabled:

dnf repolist
repo id               repo name
fedora                Fedora 45 - x86_64
fedora-cisco-openh264 Fedora 45 openh264 (From Cisco) - x86_64
updates               Fedora 45 - x86_64 - Updates

Those definitions ship in Fedora's own fedora-repos package; no third party repository is pre loaded, and nothing from fedora-cisco-openh264 is installed.

Automatic updates are armed:

systemctl is-enabled dnf5-automatic.timer && cat /etc/dnf/automatic.conf
enabled
# cloudimg: keep this Fedora Linux 45 Minimal VM patching itself.
# Overrides /usr/share/dnf5/dnf5-plugins/automatic.conf (see dnf5-automatic(8)).
[commands]
apply_updates = yes
upgrade_type = security
download_updates = yes
random_sleep = 300
reboot = never

[emitters]
emit_via = motd

Security updates are applied automatically and the machine never reboots itself. To run it now, or to turn it off:

sudo systemctl start dnf5-automatic.service
sudo systemctl disable --now dnf5-automatic.timer

Check whether a reboot is needed to activate what has been installed:

sudo dnf needs-restarting -r
Updating and loading repositories:
 Fedora 45 openh264 (From Cisco) - x86_ 100% |  17.9 KiB/s |   7.3 KiB |  00m00s
 Fedora 45 - x86_64 - Updates           100% |   5.8 MiB/s |  14.1 MiB |  00m02s
 Fedora 45 - x86_64                     100% |  12.8 MiB/s |  56.5 MiB |  00m04s
Repositories loaded.
No core libraries or services have been updated since boot-up.
Reboot should not be necessary.

Step 6: Verify the security posture

sudo sshd -T | grep -iE '^(permitrootlogin|passwordauthentication|kbdinteractiveauthentication|permitemptypasswords) '
PermitRootLogin prohibit-password
PasswordAuthentication no
KbdInteractiveAuthentication no
PermitEmptyPasswords no

OpenSSH on Fedora 45 prints these keys in mixed case, hence grep -i. PasswordAuthentication reads no on a machine created with an SSH key and yes on one created with a password: provisioning sets it from your choice, and the image does not pin it.

sudo passwd -S root && getenforce
root L 2009-12-22 -1 -1 -1 -1
Enforcing

The L means the root password is locked; the date is only the placeholder left by the Azure agent's deprovisioning and carries no meaning.

Confirm SSH is the only thing listening off the machine:

ss -tln && ss -uln
State  Recv-Q Send-Q Local Address:Port Peer Address:Port
LISTEN 0      128          0.0.0.0:22        0.0.0.0:*
LISTEN 0      4096   127.0.0.53%lo:53        0.0.0.0:*
LISTEN 0      4096      127.0.0.54:53        0.0.0.0:*
LISTEN 0      128             [::]:22           [::]:*
State  Recv-Q Send-Q Local Address:Port Peer Address:Port
UNCONN 0      0         127.0.0.54:53        0.0.0.0:*
UNCONN 0      0      127.0.0.53%lo:53        0.0.0.0:*
UNCONN 0      0          127.0.0.1:323       0.0.0.0:*
UNCONN 0      0              [::1]:323          [::]:*

Port 22 is the only port reachable from outside the machine. The port 53 sockets are systemd-resolved's DNS stubs and the port 323 sockets are chrony's control interface, all bound to loopback only. There is no port 5355 socket, because LLMNR is switched off.

Patch level, automatic security updates, SELinux, the locked root account, key only SSH and the listening ports

Step 7: Verify Azure integration

waagent --version
WALinuxAgent-2.16.0.2 running on fedora 45
Python: 3.15.2
Goal state agent: 2.16.0.2
cloud-init status --long
status: done
extended_status: done
boot_status_code: enabled-by-generator
last_update: Thu, 01 Jan 1970 00:00:30 +0000
detail: DataSourceAzure [seed=/dev/sr0]
errors: []
recoverable_errors: {}

extended_status: done rather than degraded is the result you want.

azure-vm-utils provides stable names for the operating system and resource disks, independent of whether a size presents them as SCSI or NVMe:

ls /dev/disk/azure/
os
os-part1
os-part2
os-part3
resource
resource-part1
root
root-part1
root-part2
root-part3

Confirm time synchronisation against the Azure host clock (PHC0) and that nothing failed during boot:

chronyc tracking | head -2 && systemctl list-units --state=failed
Reference ID    : 50484330 (PHC0)
Stratum         : 1
  UNIT LOAD ACTIVE SUB DESCRIPTION

0 loaded units listed.

The Azure serial console uses ttyS0:

cat /proc/cmdline | tr ' ' '\n' | grep console=
console=tty1
console=ttyS0,115200n8

Azure guest integration: the Azure Linux Agent, cloud-init, the serial console, failed units, time synchronisation and the root filesystem

Step 8: Networking and the firewall

No host firewall is installed; Fedora Cloud Edition does not ship firewalld. Your Azure Network Security Group is the firewall. The Azure Linux Agent's own protection of the Azure platform endpoint uses iptables, which is part of the Azure stack the trim protects.

If you prefer a host firewall as well (this also brings in nftables):

sudo dnf install firewalld
sudo systemctl enable --now firewalld
sudo firewall-cmd --permanent --add-service=ssh
sudo firewall-cmd --reload

Add that after you have confirmed SSH access, and always keep port 22 open.

Step 9: Install software

Install packages with dnf:

sudo dnf install nginx

Search for a package, or find which package provides a command you expected to have:

dnf -q provides /usr/bin/rsync

If you need a package that is not in Fedora's repositories, prefer a container or a language level package manager over a third party repository — third party repositories are the usual cause of a broken release upgrade later.

Step 10: Upgrading to the next Fedora release

Fedora is upgraded in place, and you should plan to do this before 8 December 2027:

sudo dnf upgrade --refresh
sudo dnf system-upgrade download --releasever=46
sudo dnf offline reboot

The machine reboots, applies the upgrade offline and reboots again. Take a snapshot of the operating system disk first, read the release notes for the version you are moving to, and try it on a test machine before a production one. A release upgrade upgrades the packages that are installed; it does not reinstall the packages removed from this image, although a new release can bring in new dependencies of its own.

Common Use Cases

  • Configuration managed hosts that want the smallest practical Fedora base on a current release
  • Security conscious deployments that want fewer installed packages to patch, scan and audit
  • Build and test hosts that need the newest Fedora toolchains on a lean, measured base

Troubleshooting

Cannot connect via SSH

Check the Network Security Group allows inbound TCP 22 from your address, that the machine is running, and that you are using the admin username you chose with the matching private key, or the password you set in the portal.

Locked out: getting back in from the Azure portal

On Fedora Linux 45, the portal's Reset password action reports success but does not change the password today: the Azure VMAccess extension that performs it does not complete its password step on Fedora 45. cloudimg measured this on this image and on the Fedora Project's own Azure image (17 November 2026); your existing password keeps working. Two portal routes do work:

  • Reset SSH public key. On the machine's Help > Reset password page choose Reset SSH public key, enter your admin username and paste a public key. The key works for SSH straight away, even if the portal then shows an error from the extension.
  • Run command. Operations > Run command > RunShellScript runs as root through the Azure Linux Agent, which is enabled on this image. For example, to add a public key for your admin user (replace both placeholders):
install -d -m 700 -o <user> -g <user> /home/<user>/.ssh
echo '<your-public-key>' >> /home/<user>/.ssh/authorized_keys
chown <user>:<user> /home/<user>/.ssh/authorized_keys
chmod 600 /home/<user>/.ssh/authorized_keys

Once you are logged in, sudo passwd <user> sets a new password.

A command I expected is missing

Find the package that provides it and install it, for example dnf provides /usr/bin/rsync then sudo dnf install rsync. The manifest header in /usr/share/cloudimg/fedora-45-minimal.manifest lists the notable removals.

Azure agent not running

sudo systemctl status waagent
sudo systemctl restart waagent

Disk is full

The root filesystem is btrfs. Grow the operating system disk in the Azure portal, then extend the filesystem:

sudo btrfs filesystem resize max /

The boot log shows error lines

On a freshly launched Standard_B2s machine, journalctl -p err -b --no-pager on its first boot shows lines like these, and all are harmless:

kernel: virt/tdx: TDX not supported by the host platform
(udev-worker)[625]: sdb: /usr/lib/udev/rules.d/60-block-scheduler.rules:3 ATTR{queue/scheduler}="bfq": Failed to write "bfq" to sysfs attribute "queue/scheduler", ignoring: Device or resource busy
kernel: I/O error, dev sr0, sector 0 op 0x0:(READ) flags 0x880700 phys_seg 1 prio class 2
kernel: I/O error, dev sr0, sector 0 op 0x0:(READ) flags 0x800000 phys_seg 2 prio class 2
kernel: Buffer I/O error on dev sr0, logical block 0, async page read
kernel: Buffer I/O error on dev sr0, logical block 1, async page read

The first is the kernel noting that the host does not offer Intel TDX confidential computing. The bfq lines are udev failing to change the I/O scheduler on a device that is busy at that moment, and carrying on — note the word ignoring; which device they name (sdb above; sr0 or sda on other boots) varies from boot to boot, and some boots show none. The sr0 I/O errors appear on the first boot only: sr0 is the virtual CD-ROM Azure uses to pass provisioning data in, and it is read once more after it has been ejected. An I/O error naming sda or sdb is a different matter and worth raising with support. Within minutes of exposing port 22 you may also see kex_exchange_identification lines from internet SSH scanners; restrict the source range on your port 22 rule if you would rather not. After you stop (deallocate) and start the machine, or Azure redeploys it to another host, the error log may also show systemd-fsck[…]: fsck failed with exit status 16. followed by Ignoring error. This is harmless too: Azure provides a fresh temporary disk, still NTFS-formatted, and the file-system check runs on it before cloud-init reformats it for /mnt. No service is left in a failed state.

Important Notes

Fedora Linux is free and open source. It is not covered by a single licence: the distribution is a collection of independently licensed packages. On this image, 367 installed packages carry 127 distinct licence strings, most commonly MIT, GPL-3.0-or-later, LGPL-2.1-or-later, GPL-2.0-or-later and BSD-3-Clause. Read any package's terms with rpm -qi <package> or under /usr/share/licenses/. No subscription, entitlement or licence key is required.

Fedora and the Infinity design logo are trademarks of Red Hat, Inc. cloudimg is not affiliated with, endorsed by or sponsored by the Fedora Project or Red Hat, and uses the name only to identify the distribution this image contains. This image is not provided or supported by the Fedora Project; support for it comes from cloudimg. Everything installed in it comes from Fedora's own repositories, and nothing from outside them is added. For the distribution itself, see fedoraproject.org.

Fedora Linux 45 was released on 3 November 2026 and reaches end of life on 8 December 2027. Check the Fedora release schedule and plan your upgrade before support ends.

Support

cloudimg's support team is on hand 24 hours a day by email for this image, with a guaranteed response within 24 hours. Contact: support@cloudimg.co.uk or https://www.cloudimg.co.uk/support