# A Runner Inside a runner using podman

**URL:** <https://drone.discourse.group/t/a-runner-inside-a-runner-using-podman/10003>\
**Category:** Drone Support\
**Created:** [July 31, 2021, 9:43pm UTC](https://drone.discourse.group/t/a-runner-inside-a-runner-using-podman/10003 "2021-07-31T21:43:25Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![lmtr\_nn](https://yyz1.discourse-cdn.com/flex003/user_avatar/drone.discourse.group/lmtr_nn/32/6379_2.png) [@lmtr\_nn](https://drone.discourse.group/u/lmtr_nn)\
**Post date:** [July 31, 2021, 9:43pm UTC](https://drone.discourse.group/t/a-runner-inside-a-runner-using-podman/10003/1 "2021-07-31T21:43:25Z")

</div>

The Idea is pretty simple, Can we use a docker container to buid the pipelines inside it, without talking to the docker outside of the container. following [this](https://www.redhat.com/sysadmin/podman-inside-container) It is possible to use podman instead of docker. And this specifies that it is possible to emulate the docker socket in podman [Use Docker Compose with Podman to Orchestrate Containers on Fedora Linux - Fedora Magazine](https://fedoramagazine.org/use-docker-compose-with-podman-to-orchestrate-containers-on-fedora/).

---

<div class="post-metadata">

**Author:** ![bradrydzewski](https://yyz1.discourse-cdn.com/flex003/user_avatar/drone.discourse.group/bradrydzewski/32/3513_2.png) [@bradrydzewski](https://drone.discourse.group/u/bradrydzewski)\
**Post date:** [August 1, 2021, 10:36pm UTC](https://drone.discourse.group/t/a-runner-inside-a-runner-using-podman/10003/2 "2021-08-01T22:36:19Z")

</div>

There are no plans to formally support Podman instead of Docker, however, please keep in mind that Drone Runners are conceptually similar to Kubernetes Operators in that anyone can create a Drone runner. See this thread:

> [@Building using alternative drone.yml](http://discuss.harness.io/t/add-podman-support/7459/2):
>
> You can retrieve the latest successful build using either the Drone API or the Drone CLI. You can then use the build number of this build to trigger a Drone deploy event: drone deploy {org}/{project} {buildNumber} {target}. As the target you could specify ‘nightly’. Then add a step to your .drone.yml file containing a deploy step for your nightlies and make sure you add this to the step’s conditions: when: event: deployment environment: nightly I think this will do exactly what you want,…

---

<div class="post-metadata">

**Author:** ![lmtr\_nn](https://yyz1.discourse-cdn.com/flex003/user_avatar/drone.discourse.group/lmtr_nn/32/6379_2.png) [@lmtr\_nn](https://drone.discourse.group/u/lmtr_nn)\
**Post date:** [August 24, 2021, 11:41pm UTC](https://drone.discourse.group/t/a-runner-inside-a-runner-using-podman/10003/3 "2021-08-24T23:41:57Z")

</div>

Hello, I discover that podman has a socket for docker compatibility and that I have successfuly started a runner with podman instead of docker.

I got interested in this build because my drone runner wasn’t building docker images and buildah also wasn’t working, now I have both working fine

Here is the how to:

you will need podman and podman-docker, in fedora and centos there are 2 different packages for each one but in ubuntu there is only podman. After installing it you will be able to verify that you have the podman server running if you can run `systemctl status podman.socket`. You must take notes of where the socket is running which can be seen in the status command

 ![image](https://canada1.discourse-cdn.com/flex003/uploads/testdrone/original/2X/5/52f92417ab312c19561139bb59154399c2aee376.png)  
As you can see, my was running in the /run/podman/podman.sock

With that out of the way, you can run the container with:

```bash
sudo podman run -d \
    -e DRONE_RPC_PROTO="https" \
    -e DRONE_RPC_HOST="YOURDOMAIN" \
    -e DRONE_RPC_SECRET="YOUR_SECRET" \
    -e DRONE_RUNNER_CAPACITY=2 \
    -e DRONE_RUNNER_NAME="NAME" \
    --restart always \
    --name runner \
    -v [YOUR_SOCKET_PATH]:/var/run/docker.sock \
    docker.io/drone/drone-runner-docker

```

Finally I recommend checking the `/etc/containers/registries.conf` to see if you got any registries configuration there, if you don’t I recommend:

```toml
unqualified-search-registries = ["docker.io"]

```