-
|
Hey Podman Community, A few days ago, I tried updating Podman to the latest version using Podman Desktop, but the process failed. Now, I'm stuck with two installations: one that's half-complete and another that's working (4.x is fine, but 5.x isn't). Every time I try to install the latest version, I get an error, even though I have around 20GB free on my C: drive and plenty of space on my D: drive. FYI, my D: drive is BTRFS (using WinBtrfs), but I doubt that's causing the issue.
I'd love some guidance on manually uninstalling the current versions, or any workarounds to get rid of 4.x and successfully install 5.x. If anyone has faced this issue or knows a fix to avoid this error during installation, please share your insights! Thanks a bunch in advance! |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 8 replies
-
|
podman-desktop is a different project and it might be worth asking over there as well. @l0rd any ideas here? |
Beta Was this translation helpful? Give feedback.
-
|
As the issue is with podman installer, and not podman-desktop, I think it won't be helpful. |
Beta Was this translation helpful? Give feedback.
-
|
It's hard to tell without logs. It's the first time I see such error. The screenshot is from the 4.6.1 installer. @aarmn did you get a similar error if trying the 5.4.0 installer? You may want to use this command from a terminal to generate some logs with more details: |
Beta Was this translation helpful? Give feedback.
-
|
Hey @l0rd , thanks for your suggestion! Seems like I cant do much from 5.4.0 setup,
Yet I can't uninstall neither of them, is there a way I can run the uninstaller setup with logs for further analysis? the log of setup file: |
Beta Was this translation helpful? Give feedback.
-
|
It can happen to have some inconsistencies in the MSI databases. What I do to remove every Podman installation is executing this commands from a terminal: $Installer = New-Object -ComObject WindowsInstaller.Installer;
$InstallerProducts = $Installer.ProductsEx("", "", 7);
$InstalledProducts = ForEach($Product in $InstallerProducts){
[PSCustomObject]@{ProductCode = $Product.ProductCode();
LocalPackage = $Product.InstallProperty("LocalPackage");
VersionString = $Product.InstallProperty("VersionString");
ProductName = $Product.InstallProperty("ProductName")
}
};
$InstalledProducts | Where-Object {$_.ProductName -match "podman"}and uninstall it with |
Beta Was this translation helpful? Give feedback.
-
|
I'm pretty sure this is not the behavior setup should have tho!
|
Beta Was this translation helpful? Give feedback.
-
|
No, this should not happen. We cannot fix the 4.6.1 installer, though. I recommend cleaning up your MSI database (there should be no more products named Podman) and retrying the latest installation. We should have released the v5.4.1 of the windows installer yesterday.
If you can't stop the other installer, try rebooting your machine. |
Beta Was this translation helpful? Give feedback.
-
|
A little update on the condition, setup automatically opens up on system login, which means, probably it somehow made it's way to runonce or run registry, or my system msi setups db is in some unimaginable way corrupted. Meanwhile my laptop charger stopped working, as soon as I can pop some issues off of the stack, I'll update this discussion with probable solutions/workarounds I found. |
Beta Was this translation helpful? Give feedback.
-
|
Final Update: I think, It was not an issue with podman setup, windows seem to have a max number of setup files and tmp lock files in Somehow this happened first when I was updating from podman 4 to 5, but I don't think it has to do with podman, rather with awful implementation of |
Beta Was this translation helpful? Give feedback.
Final Update:
I think, It was not an issue with podman setup, windows seem to have a max number of setup files and tmp lock files in
C:\windows\installersand somehow, I managed to reach the maximum and no cleaner or common ways, seemed to clean that up, meanwhile its recommended to NEVER manually delete
.tmpfiles there, I did it, and it solved my issue, sorry and thanks to everyone for their help.Somehow this happened first when I was updating from podman 4 to 5, but I don't think it has to do with podman, rather with awful implementation of
msiexec.