Added two dedicated Gitea Actions runners for Rust-heavy AutoCoder-Engine workflow jobs.
giteaConfigMap/gitea-act-runner-rust-configDeployment/gitea-act-runner-rust-1Deployment/gitea-act-runner-rust-2drg-k8s-rust-runner-1drg-k8s-rust-runner-2rust-large/mnt/fastdata/k8s-pvcs/gitea/act-runner-rust-1/mnt/fastdata/k8s-pvcs/gitea/act-runner-rust-2/var/lib/gitea-act-runner/rust-1-docker-lib/var/lib/gitea-act-runner/rust-2-docker-libThe first Docker smoke test against fastdata/NFS failed because Docker could not chown /var/lib/docker on the NFS hostPath. The rollout was revised to keep only runner registration data on fastdata and use local ext4 for Docker cache.
2/2 Running.27.5.1 and storage driver overlay2.rust-large.rust-large moved past waiting after the runners registered.The first backend image build on the new pool failed because gitea-act-runner-rust-config injected DOCKER_HOST=unix:///run/docker/docker.sock into workflow job containers. That path exists inside the runner pod, but the workflow job container expects Docker at the default /var/run/docker.sock path.
The runner-level DOCKER_HOST environment entry was removed and both Rust runner deployments were restarted. A controlled smoke test inside a gitea/runner-images:ubuntu-24.04 job-like container successfully reached Docker through /var/run/docker.sock and initialized a buildx builder.
69fff2f - Add Gitea Rust runner pool2ec2e4e - Use local Docker storage for Rust runners487e552 - Fix Rust runner Docker socket env