silverwind 2e59141ae9 fix: allow tmpfs mounts in container options (#1289) ...

Support tmpfs in container `options` via `--mount type=tmpfs,...`, like GitHub does. The `valid_volumes` check silently dropped these mounts because they have no source. A tmpfs is backed by memory and exposes nothing from the host, same as `--tmpfs`, which already passes. Every other mount still goes through the allowlist.

Both forms now work:

```yaml
services:
  mysql:
    image: mysql:8.4
    options: --tmpfs /var/lib/mysql # already worked
```

```yaml
services:
  mysql:
    image: mysql:8.4
    options: --mount type=tmpfs,destination=/var/lib/mysql # was dropped, now works
```

Reviewed-on: https://gitea.com/gitea/runner/pulls/1289
Reviewed-by: bircni <bircni@icloud.com>
Co-authored-by: silverwind <me@silverwind.io>

2026-10-06 19:19:51 +00:00

..

config_test.go

…

config.example.yaml

fix: allow tmpfs mounts in container options (#1289)

2026-10-06 19:19:51 +00:00

config.go

feat: add Kubernetes backend (#1260)

2026-10-01 06:59:15 +00:00

edit_other.go

…

edit_test.go

…

edit_unix.go

…

edit.go

…

embed.go

…

registration_test.go

…

registration.go

…