From a9087cd678e8583fb50010052350780cf7000432 Mon Sep 17 00:00:00 2001
From: Thomas Anderson <127358482+zc-devs@users.noreply.github.com>
Date: Wed, 13 Nov 2024 16:03:22 +0300
Subject: [PATCH] Podman is not (official) supported (#4367)

---
 docs/docs/30-administration/22-backends/10-docker.md | 10 ++++++----
 1 file changed, 6 insertions(+), 4 deletions(-)

diff --git a/docs/docs/30-administration/22-backends/10-docker.md b/docs/docs/30-administration/22-backends/10-docker.md
index 3e5db5b52..d3a78fd93 100644
--- a/docs/docs/30-administration/22-backends/10-docker.md
+++ b/docs/docs/30-administration/22-backends/10-docker.md
@@ -18,10 +18,6 @@ FROM woodpeckerci/woodpecker-server:latest-alpine
 RUN apk add -U --no-cache docker-credential-ecr-login
 ```
 
-## Podman support
-
-While the agent was developed with Docker/Moby, Podman can also be used by setting the environment variable `DOCKER_HOST` to point to the Podman socket. In order to work without workarounds, Podman 4.0 (or above) is required.
-
 ## Image cleanup
 
 The agent **will not** automatically remove images from the host. This task should be managed by the host system. For example, you can use a cron job to periodically do clean-up tasks for the CI runner.
@@ -44,6 +40,12 @@ docker image rm $(docker images --filter "dangling=true" -q --no-trunc)
 docker volume rm $(docker volume ls --filter name=^wp_* --filter dangling=true  -q)
 ```
 
+## Tips and tricks
+
+### Podman
+
+There is no official support for Podman, but one can try to set the environment variable `DOCKER_HOST` to point to the Podman socket. It might work. See also the [Blog posts](https://woodpecker-ci.org/blog).
+
 ## Configuration
 
 ### `WOODPECKER_BACKEND_DOCKER_NETWORK`