Assuming you’re doing everything as root, but if you aren’t then prefix these commands with sudo as appropriate for your environment.

dnf config-manager --add-repo https://download.docker.com/linux/centos/docker-ce.repo
dnf install -y docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin
systemctl enable --now docker

That’s it. Done. Now if you want to allow non-root users to use docker.

 usermod -aG docker user   # user is the non-root user you want to be able to use docker

You’ve probably tried to build a bootable USB drive and it hasn’t copied the image correctly.

I highly recommend using rufus in DD mode. This has always worked for me.

Install the required packages

You will need to install the cifs-utils package to mount a network drive on an Ubuntu Linux system.

sudo apt-get install -y cifs-utils

For a Red Hat based system you will also need the cifs-utils package, installed by dnf

sudo dnf install -y cifs-utils

Create a mount point

Create a mount point for the CIFS share. eg.

sudo mkdir /srv/cifs/<share>      # where '<share>' is the name of the share you want mounted

Create a credentials file

sudo vim /etc/credentials.<share>   # where '<share>' is the name of the share you want mounted

Add the following contents to the credentials file, updating with your userid/password details to access your share.

username=<shareuser>
password=<sharepassword>

Make sure the credentials file is only visible to root

sudo chown root:root /etc/credentials.<share>      # where '<share>' is the name of the share you want mounted
sudo chmod 600 /etc/credentials.<share>

Add the mount to /etc/fstab

To mount the network drive permanently, you need to add an entry to the /etc/fstab file to ensure the share is mounted automatically when the system boots.

Open the /etc/fstab file in a text editor and add the following line:

//<ip address of your cifs server>/<share> /srv/cifs/<share> cifs credentials=/etc/credentials.<share> 0 0

Testing the mount

sudo mount -a
df -h

This should show the CIFS share mounted at the specified mount point.

There are still a few issues with AlmaLinux 9, not because of AlmaLinux, but because the oVirt engine force enables a bunch of Centos 9 Stream repositories breaking the system. You can get around this by basically disabling those repositories in /etc/yum.repos.d/ as they appear – bugs will be filed with the engine.

sudo rpm --import https://packages.microsoft.com/keys/microsoft.asc

Step 2. Add the repository

echo -e  "[vscode]\nname=packages.microsoft.com\nbaseurl=https://packages.microsoft.com/yumrepos/vscode/\nenabled=1\ngpgcheck=1\nrepo_gpgcheck=1\ngpgkey=https://packages.microsoft.com/keys/microsoft.asc\nmetadata_expire=1h" | sudo tee -a /etc/yum.repos.d/vscode.repo

Step 3. Refresh the yum meta data

sudo dnf update -y

Step 4. Install vscode

sudo dnf install code -y

sudo rpm --import https://packages.microsoft.com/keys/microsoft.asc

Step 2. Add the repos

sudo dnf config-manager --add-repo https://packages.microsoft.com/yumrepos/edge

Step 3. Refresh the yum meta data

sudo dnf update --refresh

Step 4. Install Edge

sudo dnf install microsoft-edge-stable

Microsoft Edge should now be available for you to use either via the CLI or the Gnome Deskop

That being said though, the WSL vhdx files can grow as you’re doing Linux work and while you can (and should) clean up side the Linux environment it’s not reflected back to windows as free space.

So how do you compact your WSL file?

1. Shutdown your WSL system.
   
   wsl.exe --list --verbose # note the verbose is required to get the state


wsl.exe --terminate Ubuntu-24.04
   
   
2. Shrink the disk using diskpart
   
   diskpart
   
   
   
   You need to select the vhdx file for your WSL instance. The VHDX file is typically found in your AppData folder. In my case it was this.
   
   
   
   I copy the VHDX file location as a path.
   
   
   
   DISKPART> select vdisk file="C:\Users\geoff\AppData\Local\Packages\CanonicalGroupLimited.Ubuntu24.04LTS_79rhkp1fndgsc\LocalState\ext4.vhdx"
   
   
   
3. Compact the vdisk
   
   DISKPART> compact vdisk
   
   
   
4. The results.
   
   BEFORE
   
   
   
   AFTER
   
   
   
   As you can see, i’ve freed up nearly 6Gb.
   

Firstly, do you have WSL2 installed? If not, then this will help https://learn.microsoft.com/en-us/windows/wsl/install-manual#step-1—enable-the-windows-subsystem-for-linux

In order to best use WSL, you of course need to have a distribution installed. Ubuntu is one of the easiest and most common to install.

wsl --list --online           #check what distros are available
wsl --install -d Ubuntu-24.04 #latest at the time of writing

Now that you have a distro installed, we have something to configure. There are 2 configuration files that customise the distribution experience under WSL2. wsl.conf and .wslconfig

wsl.conf contains per-distribution settings, whereas .wslconfig configures global settings for the WSL2 environment.

wsl.conf is stored in the /etc directory within the distribution.

.wslconfig is stored in your %UserProfile% folder.

.wslconfig

The .wslconfig file is in .ini format with the GA features found under section [wsl2]. There is also an [experimental] section for unreleased options.

Note: All options may not be available to you as they are Windows OS and WSL version dependent. You can reasonably assume if you are running Windows 11, 22H2 or higher that most of the options described below are available to you. This is not the complete list, just the one’s I have found to be quite useful

GA features that I find useful

Accessible via the [wsl2] section of the .wslconfig file

Experimental (though very useful) features

Accessible via [experimental] section of the .wslconfig file.

wsl.conf

As I mentioned above the /etc/wsl.conf within the distribution controls some interesting behaviours, especially on distro launch.

[boot]

systemd=true

Solves the problem where you’re reliant on systemd resources within your WSL2 distro. I normally have it turned on.

[automount]

Some things to note.

Windows disks are mounted using Drvfs and are by default case sensitive. You can override this behaviour for all or single drives. More information is available at Per-directory case sensitivity and WSL – Windows Command Line (microsoft.com)

[network]

Release notes for 0.1.5 can be found over at github at Release Milestone 0.1.5 · gocallag/hyperv (github.com)

Further information on upcoming milestones and their associated features can be found at Milestones – gocallag/hyperv (github.com)

What’s Changed

• Added Feature to vm_info to provide search capability by Name
• Closed Issue 2 – Feature to allow vm info to search by power state and names
• BugFIX: Use the convertto-json , convertfrom-json to avoid loop in Exit-Json (limiting depth)
• Closed Test Issue: Added verifier for vm_info module checks and cleanups
• Closed Test Issue: Added basic asserts for switch_info testing via molecule
• Closed Test Issue: Added verifier asserts for switch module as part of molecule testing
• Closed Test Issue: Added assert based testing for vm module as part of molecule
• BugFIX, Issue 12: bug vm info fails molecule verifier on running vm check

Feedback / Requests welcome.

You can find it over at gocallag/hyperv (github.com)