Skip to main content

Error upgrading Podman

If you are using Podman Desktop, you are in fact using a combination of 2 tools. One is Podman, an open source container, pod, and container image management engine.

The other is Podman Desktop itself which is a graphical layer on top of Podman (and other container engines).

Podman Logo

This means that you can use different versions of Podman in combination with different versions of Podman Desktop.  For example, as you can see in the screenshot below I’m using version 5.2.0 of Podman whereas my Podman Desktop version is v1.12.0.

Error: vm "podman-machine-default" already exists on hypervisor

Today after upgrading Podman, Podman Desktop started to return the following error message when I tried to initialize the podman virtual machine:

Error: vm "podman-machine-default" already exists on hypervisor


I tried to fix it by removing the virtual machine distribution from wsl:

wsl --unregister podman-machine-default

When I tried to initialize the podman virtual machine again, it failed again but with a different error message:

Error extracting compressed file: \"unexpected EOF\"" Error: unexpected EOF

To fix that problem I had to reset the virtual machine:

podman.exe machine reset
Warning: this command will delete all existing Podman machines and all of the configuration and data directories for Podman machines
The following machine(s) will be deleted:

Are you sure you want to continue? [y/N]

Now I could re-download and initialize the virtual machine successfully:

podman.exe machine init
Downloading VM image: v20240728061533-5.1-rootfs-amd64.tar.zst: done
Extracting compressed file: podman-machine-default-amd64: done
Importing operating system into WSL (this may take a few minutes on a new WSL install)...
Import in progress, this may take a few minutes.
The operation completed successfully.
Configuring system... Machine init complete

To start your machine run: podman machine start

More information

Podman (podman.io)

Podman Desktop (podman-desktop.io)

podman-machine-init — Podman documentation

Popular posts from this blog

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...

Cleaner switch expressions with pattern matching in C#

Ever find yourself mapping multiple string values to the same result? Being a C# developer for a long time, I sometimes forget that the C# has evolved so I still dare to chain case labels or reach for a dictionary. Of course with pattern matching this is no longer necessary. With pattern matching, you can express things inline, declaratively, and with zero repetition. A small example I was working on a small script that should invoke different actions depending on the environment. As our developers were using different variations for the same environment e.g.  "tst" alongside "test" , "prd" alongside "prod" .  We asked to streamline this a long time ago, but as these things happen, we still see variations in the wild. This brought me to the following code that is a perfect example for pattern matching: The or keyword here is a logical pattern combinator , not a boolean operator. It matches if either of the specified pattern...