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

[ScrewTSW]

Bug description

Currently Global Onboarding is forcing a reboot after WSL2 requirement installation (makes sense, 100% valid)

However as a side-effect of this, some of the Global Onboarding is never executed on a fresh installation of Windows that was untouched by Podman or Podman Desktop in the past

After the reboot, only a "Podman needs to be set up" notification is shown in system tray, on which upon clicking the Dashboard is opened.

User may resume onboarding individual items manually from there on, but in my opinion that pretty much defeats the purpose of Global Onboarding

I see this as a detrement to user experience. Input needed (PM/architect).

Operating system

Windows 10, 22H2

Installation Method

Installer from website/GitHub releases

Version

1.8.0

Steps to reproduce

Preparation:

• Clean up %HOME%/.local/share/containers
• Clean up %HOME%/.config/containers
• Clean up %AppData%/Local/Microsoft/WindowsApps
• Clean up %AppData%/Roaming/Podman\ Desktop/
• Properly uninstall WSL, Podman
• Disable WSL and Virtualization Platform

Onboarding:

• Download and run latest Windows installer
• Follow onboarding steps (manually enable Virtualization Platform /norestart)
• Click Install WSL2 button in Global Onboarding
• Perform required reboot

After restart:

• Podman needs to be set up notification is displayed in systray
• Upon clicking Dashboard is opened

Relevant log output

No response

Additional context

[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)