Onboarding: Windows - Global Onboarding is not resumed after required reboot (WSL2 installation) about podman-desktop

[odockal]

Assuming that global onboarding in one-time on-startup thing, you have decided to skip it first, if assumptions are confirmed, then the behavior is alright, imho. If you choose to onboard kubectl, compose and podman, then podman is executed as the last and so the restart is fine since you have already onboarded the previous two.
Push up notification is only tied to podman and podman-machine.

[ScrewTSW]

Assuming that global onboarding in one-time on-startup thing, you have decided to skip it first, if assumptions are confirmed, then the behavior is alright, imho. If you choose to onboard kubectl, compose and podman, then podman is executed as the last and so the restart is fine since you have already onboarded the previous two. Push up notification is only tied to podman and podman-machine.

Correct. I've missed the fact that docker-compose and kubectl are onboarded before Podman which renders that part mute. My bad.

However, it still means that machine creation and podman configuration has to be triggered manually via the old approach - Onboarding/Dashboard

[benoitf]

I think that in case of reboot we could display again the global onboarding
(in case user didn't press any skip button)