service/ci.md

@@ -680,10 +680,8 @@ We currently use the following tags:
    example, run Docker-inside-Docker (DinD), note that `docker` can
    also mean a `podman` runner, which is tagged on top of `docker`, as
    a feature
- * **memory** size: `64GB`, `32GB`, `4GB`, etc.
  * **hosting** provider:
    * `tpa`: runners managed by the sysadmin team
-   * `fdroid`: provided as a courtesy by the [F-Droid project](https://f-droid.org/)
    * `osuosl`: runners provided by the [OSUOSL](https://osuosl.org/)
  * **features**:
    * `privileged`: those containers have actual root access and should
@@ -694,8 +692,6 @@ We currently use the following tags:
      one such job may run at a time on a given runner
    * `verylarge`: same as `large`, with sysctl tweaks to allow high
      numbers of processes (runners with >1TB memory)
-   * `podman`: a `docker` executor which talks to the `podman` socket
-     instead of Docker, might be better suited to build container images
  * **runner name**: for debugging purposes only! allows pipelines to
    target a specific runner, do not use as runners can come and go
    without prior warning