gitlab runners seem to have started using 32-bit docker images last night ...?
Starting in the middle of pipeline https://gitlab.torproject.org/jnewsome/sponsor-61-sims/-/pipelines/176734
job run-sim-1 appears to have run on a 64-bit system as expected. The early init is gone from the console, the raw log show using an amd64 docker in the first few lines:
[0KUsing docker image sha256:cbc66ba6b5bce392231db6f027f739b88d949e2217b83a86d29e2380256a472a for debian:bookworm-slim with digest docker.io/amd64/debian@sha256:804194b909ef23fb995d9412c9378fb3505fe2427b70f3cc425339e48a828fca ...[0;m
The next job in the pipeline, on the same runner, run-sim-2 (EDIT: fixed the link to point to first instance of this job instead of a later retry), and all subsequent jobs in subsequent pipelines I've tried to run in this project (including jobs that use other runners), appear to be running on i386.
Using docker image sha256:b53f4571eaf2e6d0a291cfb44bb6c020e5053f8aaa351c9702ad385f28dcc9c2 for debian:bookworm-slim with digest docker.io/i386/debian@sha256:f9865861c5ed8a0b521347da4aae9aa69edc278a0bad41364ad6f40546ed1520 ...
Could this be a change on the runner configs? I don't see how it could be a change on my end since it happened mid-pipeline XD