{
  "id": 5957493,
  "title": "Setting Up Podman Desktop So the Same Containers Work on Both Windows and WSL2",
  "url": "https://urgent.news/2026/09/06/setting-up-podman-desktop-so-the-same-containers-work-on-both-windows",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-09-06T10:45:06.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/onlyutkarsh/setting-up-podman-desktop-so-the-same-containers-work-on-both-windows-and-wsl2-3mc5"
  },
  "original_language": "en",
  "account": "Podman Desktop aims to allow running containers seamlessly across Windows and WSL2 environments. This ensures only one container instance is running, accessible from both shells. Benefits include natural cross-shell work, avoiding duplicate resources, and consistent debugging. A single Linux VM, 'podman-machine-default', serves as the container engine accessible via SSH from both PowerShell and WSL2.\n\nConnection to Podman Desktop's VM is established through SSH. Two connection types are present: rootless (user) and rootful (root). Rootless is recommended for typical development due to predictable file ownership and better isolation. However, rootful is needed for privileged ports or specific system capabilities.\n\nCommon issues arise when setting up the connection.\n\nFirstly, the Podman Desktop machine must be set to rootless mode. Even after configuring a default connection, Podman CLI errors might occur if the machine defaults to rootful. To resolve this, stop the machine, set the rootful flag to false, restart, and verify the change.\n\nSecondly, WSL's local Podman CLI is unaware of the Windows machine. Installing Podman in WSL and adding a connection using the correct URI and port from PowerShell ensures Podman Desktop's VM is the target for WSL's container commands. Without adding the connection, WSL commands may fail silently due to hardcoded ports.\n\nLastly, Podman Desktop's assigned SSH port is dynamic and changes with machine restarts. Failing to update WSL's connection port when Podman Desktop restarts can result in connection errors. Regularly syncing WSL's connection with the current port ensures uninterrupted communication between shells.",
  "summary": "The main goal of this setup is simple: run a container once, and access that exact same container from both PowerShell and WSL2, not two separate copies running in isolation. There are some genuine benefits with this setup in my opinion. Work across both shells naturally: I am on WSL for almost everything but occasionally I also use PowerShell for Windows side tasks. Having one engine means I…",
  "key_points": [],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}