Aspire's publish pipeline calls docker directly and crashes — even if you have Podman installed and ASPIRE_CONTAINER_RUNTIME=podman set.
ASPIRE_CONTAINER_RUNTIME only controls container image builds. The publish pipeline's compose steps (docker-compose-down, docker-compose-up) doesn't seem to work with podman right now (as of 2026-03-18, 13.1.2).
Create a fake docker command that forwards everything to Podman. Aspire calls docker, Podman answers. Done.
docker.cmd
@echo off
podman %*docker-compose.cmd
@echo off
podman compose %*Look for a user-local folder thats on the PATH like C:\Users\<you>\AppData\Local\Microsoft\WindowsApps. You can write there without admin rights.
$env:PATH -split ';' | Where-Object { Test-Path $_ }Open a new terminal and run:
docker --version
docker-compose --versionBoth should report Podman's version.