The build-push-action was trying to use docker-container driver by default, which requires privileged mount operations. This fails on unprivileged runners with vfs storage driver. Solution: Explicitly configure buildx to use 'docker' driver, which uses the regular Docker daemon that's already running with vfs storage. This avoids the need for privileged container mounts. Resolves: operation not permitted during buildkit mount Reviewed-on: graham/towerops-web#219 |
||
|---|---|---|
| .. | ||
| e2e-tests.yaml | ||
| pr-tests.yaml | ||
| production.yaml | ||
| renovate.yaml | ||
| staging.yaml | ||