containers
Setup Podman Push notification is being pushed every couple of seconds and in the tasks list there are hunders of them
Bug description
Operating system
Mac OS 14 M2
Installation Method
Installer from website/GitHub releases
Version
1.9.0
Steps to reproduce
Not sure. I was running podman desktop fo some time, and noticed the amount of notifications when I was building a bootc image. It seems unrelated. Problem is that the notification is being pushed once every couple of seconds but does take into account if the notification already was pushed. It might cause some some troubles with insufficient memory and program freezes once there is a huge amount of the notification loaded in memory, depends on the how is it implemented. Just thinking out loud.
Relevant log output
No response
Additional context
No response
FWIW I hit this too on a dev build (and it was super annoying since each popup opened a window), but then I didn't see it again after a restart/moving to another build. At the time I assumed something local was corrupt but appears to be more general.
Bug description
Operating system
Mac OS 14 M2
Installation Method
Installer from website/GitHub releases
Version
1.9.0
Steps to reproduce
Not sure. I was running podman desktop fo some time, and noticed the amount of notifications when I was building a bootc image. It seems unrelated. Problem is that the notification is being pushed once every couple of seconds but does take into account if the notification already was pushed. It might cause some some troubles with insufficient memory and program freezes once there is a huge amount of the notification loaded in memory, depends on the how is it implemented. Just thinking out loud.
Relevant log output
No response
Additional context
No response
I'm assuming it's not extension related from bootc? Or just in general / non related to the extension?
@cdrage @deboer-tim It is not bootc related I believe. I just discovered it during it. I think it is connected to the fact that the upgrade of the podman happened to the v5 and I did not purge the previous artifacts. It is highly possible to be related to #6654.
@odockal can you check if either of the following folders exist, and if they are empty?
/Users/<user>/.local/share/containers/podman/machine/qemu
/Users/<user>/.config/containers/podman/machine/qemu
I had tested the migration on an earlier version where these folders weren't cleaned up. I then moved to a newer dev build that started this notification, but onboarding failed to clean them up so the notifications kept happening every 5s indefinitely, which was super annoying. Moving up to a more recent build and going through the onboarding one more time they were finally cleaned up though.
If we confirm that's what the problem is, maybe you or @cdrage can just run a bootc build to make sure there's nothing triggering these folders to be recreated? I'm on a slow connection for most of today and have no bootable containers cached so it'll be a while before I can test.
Just following up - I have not seen these folders recreated, so for me I'm pretty sure it was just due to failed cleanup on previous migration code.
@deboer-tim I have seen this again. TRuly again after migration from podman v4 to podman v5 without removing the machine prior to podman 5 installation. (intentionally).