Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Azure Linux delivers language runtimes and development tools as RPM packages. Query the production repositories for current package names and versions instead of relying on a fixed runtime list.
Discover language runtimes
Search the repositories enabled on your system:
dnf search python
dnf search dotnet
dnf search openjdk
dnf search nodejs
dnf search golang
dnf search rust
For instructions to inspect package details and dependencies and install the runtime you select, see Manage packages with DNF.
A package being searchable or installable doesn't by itself define a long-term runtime support commitment. Review the package's repository, maintenance policy, changelog, and release notes when you choose a runtime version.
Verify installed runtime versions
Use both the runtime command and RPM metadata when you collect version information. Replace <RUNTIME_COMMAND> with the command that starts your runtime, and <PACKAGE_NAME> with its package name. For Python, for example, use python3 for both:
<RUNTIME_COMMAND> --version
rpm -q <PACKAGE_NAME>
dnf info --installed <PACKAGE_NAME>
RPM metadata identifies the exact Azure Linux package release even when the runtime reports only its upstream version.
Understand the filesystem layout
Azure Linux uses standard Linux filesystem locations. Common locations include:
| Path | Purpose |
|---|---|
/etc |
System and application configuration. |
/usr/bin and /usr/sbin |
Executable programs and administrative commands. |
/usr/lib and /usr/lib64 |
Libraries and package-managed runtime files. |
/var |
Variable data, including logs, caches, and service state. |
/opt |
Optional application software. |
/home |
User home directories. |
/run |
Runtime state that doesn't persist across restarts. |
Don't depend on a library, executable, or configuration path only because it existed in Azure Linux 3. Package renames, versioned runtime streams, and updated upstream layouts can change package-owned paths in Azure Linux 4.
Find package-owned files
List all files installed by a package:
rpm -ql <PACKAGE_NAME>
Identify which package owns a path:
rpm -qf <PATH>
Verify that package-owned files haven't changed:
sudo rpm -V <PACKAGE_NAME>
Query an RPM file before installing it. Replace <RPM_PATH> with the path to
the .rpm file you downloaded.
rpm -qlp <RPM_PATH>
rpm -qpR <RPM_PATH>
Use RPM ownership and metadata as the source of truth for package-managed paths. Avoid manually replacing package-owned files or creating compatibility links unless the application vendor documents that configuration.
Identify the operating system and mounted filesystems
Identify the distribution and version, and then inspect how the system mounts its filesystems.
Identify the operating system
Use /etc/os-release to identify Azure Linux:
cat /etc/os-release
The output includes the distribution identity and version. For example:
...
ID=azurelinux
ID_LIKE=fedora
VERSION_ID=4.0
...
Inspect mounted filesystems
Use standard storage commands to inspect mounted filesystems and paths:
findmnt
findmnt /
lsblk --fs
df -T
cat /proc/self/mounts
The filesystem type and mount layout can differ between Marketplace images, custom images, and attached data disks. Inspect the running system instead of assuming a fixed device name or mount layout.
Validate an application migration
When you move an application from Azure Linux 3 to Azure Linux 4:
- Resolve runtime packages from Azure Linux 4 production repositories.
- Rebuild native dependencies and language extensions on Azure Linux 4.
- Replace hard-coded paths with package discovery or configuration where possible.
- Use
rpm -qfandrpm -qlto confirm package ownership and installed locations. - Test configuration, service startup, logging, data paths, and upgrades in a nonproduction environment.
- Record the exact RPM versions used in the validated deployment.