Finally Got My Corporate PC to work
After installing VMWare Workstation Pro
Run these commands to get CoreOs booting
$Env:CONFIG_ENCODING="base64"$Env:CONFIG_ENCODED="ewogICJpZ25pdGlvbiI6IHsKICAgICJ2ZXJzaW9uIjogIjMuMS4wIgogIH0sCiAgInBhc3N3ZCI6IHsKICAgICJ1c2VycyI6IFsKICAgICAgewogICAgICAgICJuYW1lIjogImNvcmUiLAogICAgICAgICJzc2hBdXRob3JpemVkS2V5cyI6IFsKICAgICAgICAgICJlY2RzYS1zaGEyLW5pc3RwMzg0IEFBQUFFMlZqWkhOaExYTm9ZVEl0Ym1semRIQXpPRFFBQUFBSWJtbHpkSEF6T0RRQUFBQmhCUE5hOTJFTHBGWmxQV3RvVFNDRGwrMkdBbVp0aDRndi9TZmVkLzZXb3k5cEdzTGZ6K1h1RUoxYlFGY25nSGp3N1NieTI0OStRTElWdWtvN1c2WVBGSVFqYVNiVlBHL1BGaDZjUm0rZm9pN0xyWGRBa3pkZ3Vqc3pnV2tVNVNJQWtRPT0iCiAgICAgICAgXQogICAgICB9LAogICAgICB7CiAgICAgICAgIm5hbWUiOiAicm9vdCIsCiAgICAgICAgInNzaEF1dGhvcml6ZWRLZXlzIjogWwogICAgICAgICAgImVjZHNhLXNoYTItbmlzdHAzODQgQUFBQUUyVmpaSE5oTFhOb1lUSXRibWx6ZEhBek9EUUFBQUFJYm1semRIQXpPRFFBQUFCaEJQTmE5MkVMcEZabFBXdG9UU0NEbCsyR0FtWnRoNGd2L1NmZWQvNldveTlwR3NMZnorWHVFSjFiUUZjbmdIanc3U2J5MjQ5K1FMSVZ1a283VzZZUEZJUWphU2JWUEcvUEZoNmNSbStmb2k3THJYZEFremRndWpzemdXa1U1U0lBa1E9PSIKICAgICAgICBdCiAgICAgIH0KICAgIF0KICB9LAogICJzdG9yYWdlIjogewogICAgImZpbGVzIjogWwogICAgICB7CiAgICAgICAgIm92ZXJ3cml0ZSI6IHRydWUsCiAgICAgICAgInBhdGgiOiAiL2V0Yy9ob3N0bmFtZSIsCiAgICAgICAgImNvbnRlbnRzIjogewogICAgICAgICAgInNvdXJjZSI6ICJkYXRhOixwb2RtYW4tYm94LXByaXZhdGUiCiAgICAgICAgfSwKICAgICAgICAibW9kZSI6IDQyMAogICAgICB9CiAgICBdCiAgfSwKICAic3lzdGVtZCI6IHsKICAgICJ1bml0cyI6IFsKICAgICAgewogICAgICAgICJlbmFibGVkIjogdHJ1ZSwKICAgICAgICAibmFtZSI6ICJwb2RtYW4uc29ja2V0IgogICAgICB9CiAgICBdCiAgfQp9"
$Env:VM_NAME="podman-box"$Env:FCOS_OVA="C:\Users\m24669\Downloads\fedora-coreos-42.20250623.3.1-vmware.x86_64.ova"$Env:LIBRARY="C:\Users\m24669\tools\vmware"cd "C:\Program Files (x86)\VMware\VMware Workstation\OVFTool".\ovftool.exe --powerOffTarget --name="$Env:VM_NAME" --net:"NAT" --allowExtraConfig --extraConfig:guestinfo.ignition.config.data.encoding="$Env:CONFIG_ENCODING" --extraConfig:guestinfo.ignition.config.data="$Env:CONFIG_ENCODED" "$Env:FCOS_OVA" "$Env:LIBRARY"TIP remember base64 sometimes needs padding, coreos are a bit strict. Some encoders are not!
If for some reason network is not NAT’ED change it in VMare UI
Edit HOST file
ADD
192.168.226.128 container-box.development## Add DOCKER compability env
DOCKER_HOST = tcp://container-box.development:24079
Bonus
powercfg /powerthrottling disable /path "C:\Program Files (x86)\VMware\VMware Workstation\x64\vmware-vmx.exe"accept new key
ssh -i "C:\Users\uid\.ssh\root-podbox-ecdsa" root@container-box.development -p 22