Skip to main content

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                    VM TYPE     CREATED       LAST UP     CPUS        MEMORY      DISK SIZE

podman-machine-default  wsl         6 months ago  4 days ago  2           2GiB        100GiB

The machine is still there so that is good news. Let’s try to restart it:

>podman machine stop

Machine "podman-machine-default" stopped successfully

>podman machine start

Starting machine "podman-machine-default"

The operation timed out because a response was not received from the virtual machine or container.

Error code: Wsl/Service/CreateInstance/CreateVm/HCS_E_CONNECTION_TIMEOUT

Error: the WSL bootstrap script failed: command C:\Users\<user>\AppData\Local\Microsoft\WindowsApps\wsl.exe [-u root -d podman-machine-default /root/bootstrap] failed: exit status 0xffffffff

Looks like something is wrong with the VM. Lets remove it:

>podman machine rm podman-machine-default

The following files will be deleted:

C:\Users\<user>\.config\containers\podman\machine\wsl\podman-machine-default.json

C:\Users\<user>\AppData\Local\Temp\podman\podman-machine-default.sock

C:\Users\<user>\AppData\Local\Temp\podman\podman-machine-default-gvproxy.sock

C:\Users\<user>\AppData\Local\Temp\podman\podman-machine-default-api.sock

C:\Users\<user>\AppData\Local\Temp\podman\podman-machine-default.log

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

Logging out.

The operation has completed.

Once the VM is removed, we can try to recreate it:

>podman machine init

Looking up Podman Machine image at quay.io/podman/machine-os-wsl:5.3 to create VM

Getting image source signatures

Copying blob 54c816116e80 done   |

Copying config 44136fa355 done   |

Writing manifest to image destination

54c816116e80d74b8e638baf1fb37f3d6c4b6545f8c405d998169513766e1dc5

Extracting compressed file: podman-machine-default-amd64: done

Importing operating system into WSL (this may take a few minutes on a new WSL install)...

Importeren wordt uitgevoerd. Dit kan enkele minuten duren.

The operation timed out because a response was not received from the virtual machine or container.

Error code: Wsl/Service/RegisterDistro/CreateVm/HCS_E_CONNECTION_TIMEOUT

Error: the WSL import of guest OS failed: command C:\Users\<user>\AppData\Local\Microsoft\WindowsApps\wsl.exe [--import podman-machine-default C:\Users\<user>\.local\share\containers\podman\machine\wsl\wsldist\podman-machine-default C:\Users\<user>\.local\share\containers\podman\machine\wsl\podman-machine-default-amd64 --version 2] failed: exit status 0xffffffff

Still no luck! But what do you do if everything else failed…

A reboot!

We rebooted the machine and indeed the error magically disappeared.

On to the next issue…

More information

Error upgrading Podman

Podman 5.3.1 - Error: unable to connect to Podman socket: open \.ssh\known_hosts:

Podman Desktop–The WSL import of guest OS failed: exit status 0xffffffff

Labels:

Popular posts from this blog

.NET 8–Keyed/Named Services

A feature that a lot of IoC container libraries support but that was missing in the default DI container provided by Microsoft is the support for Keyed or Named Services. This feature allows you to register the same type multiple times using different names, allowing you to resolve a specific instance based on the circumstances. Although there is some controversy if supporting this feature is a good idea or not, it certainly can be handy. To support this feature a new interface IKeyedServiceProvider got introduced in .NET 8 providing 2 new methods on our ServiceProvider instance: object? GetKeyedService(Type serviceType, object? serviceKey); object GetRequiredKeyedService(Type serviceType, object? serviceKey); To use it, we need to register our service using one of the new extension methods: Resolving the service can be done either through the FromKeyedServices attribute: or by injecting the IKeyedServiceProvider interface and calling the GetRequiredKeyedServic...
Read more

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.
Read more

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...
Read more