docs: added _Accessing resources behind a VPN with Podman on Windows_ (…

…containers#3577)

Co-authored-by: Frederik Schwarzer <70687497+fschwa@users.noreply.github.com>
Co-authored-by: Charlie Drage <charlie@charliedrage.com>

website/docs/proxy/index.md

@@ -13,4 +13,5 @@ You can use Podman Desktop behind a proxy in various situations, such as:
 - [Using a proxy on Windows and macOS](proxy/using-a-proxy)
 - [Using a proxy requiring a custom Certificate Authorities on macOS and Windows](proxy/using-a-proxy-requiring-a-custom-ca)
 - [Using a proxy on Linux](proxy/using-a-proxy-on-linux)
-- [Using a proxy in your containers](proxy/using-a-proxy-in-your-containers.md)
+- [Using a proxy in your containers](proxy/using-a-proxy-in-your-containers)
+- [Accessing resources behind a VPN with Podman on Windows](proxy/using-a-vpn-on-windows)

website/docs/proxy/using-a-vpn-on-windows.md

@@ -0,0 +1,24 @@
+---
+sidebar_position: 5
+title: Podman behind a VPN on Windows
+description: Accessing resources behind a VPN with Podman on Windows
+tags: [podman, vpn, windows]
+keywords: [podman, vpn, windows]
+---
+
+# Accessing resources behind a VPN with Podman on Windows
+
+On Windows, if Podman needs to access resources behind a user-controlled VPN, enable user mode networking in your Podman machine.
+
+#### Prerequisites
+
+- Windows host with updated WSL2.
+- Podman 4.6.0 or greater.
+
+#### Procedure
+
+- When creating the Podman machine, select the **User mode networking (traffic relayed by a user process)** option to enable user mode networking.
+
+#### Verification
+
+- You can now access resources that are behind the VPN.

website/docs/troubleshooting/troubleshooting-podman-on-windows.md

@@ -53,6 +53,14 @@ You can find here troubleshooting help for issues specific to Windows.
 
 - Set the environment variable `ELECTRON_NO_ATTACH_CONSOLE` to true before launching Podman Desktop.
 
+## When the host is behind a VPN, Podman cannot access network resources
+
+When the host is behind a VPN, Podman might fail to access network resources, and display errors such as _Temporary failure in name resolution_.
+
+### Solution
+
+See [Accessing resources behind a VPN with Podman on Windows](/docs/proxy/using-a-vpn-on-windows).
+
 ## Older WSL versions might lead to networking issues
 
 Older versions of WSL might cause networking issues, such as the `Get-NetTCPConnection` error, indicating that the WSL loopback forwarding facility is not functioning correctly. Recent versions of WSL do not have this issue