tree 4fcbf51b88c2620056d1ee1c17e025dd936bf645
parent a0de8c9d09c5f59bf949c30ea6ffbe4d2a6c4219
author James Leitch <me@rickvanprim.com> 1701692726 -0800
committer GitHub <noreply@github.com> 1701692726 +0100
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJlbcU2CRBK7hj4Ov3rIwAAxp0IAHJsxYY4ZeiH0S5w0nXuWKuN
 zL3E7xbF5T8HecgURsrw1sbv7oz/XIcaSC5RwEoKpRm67NjYyRVnxPB3M/kSssyC
 +vIRmDvPFM2zDVCzx8NDVrmTfAq2jVL1VgeBAr1CkIIXyX8UK5OmpDbXggsDEO8e
 I64Z7K5Sd1I8XQ4DlOOtmGR/z/ssouPg1avvCxyKaJ5spLK+miFWuZFhU3WUEhou
 FYugxk8oi32S4/l64unX4W2QNYjmp84w2iZKPK+M8SD0Zso6oR75e0KFrTkEf00T
 ue3Fg/iZja39gPiSbc15uAziIyrfAFOedEQCfvCvX1kDqrw8f8VgiuLCfZbxAGg=
 =t88w
 -----END PGP SIGNATURE-----
 

Ubuntu (Nix) container removed (#1827)

**EDIT**: Based on the iteration here, I realized that I could in fact
install Nix in single-user mode as part of the `setup` phase of
`bazelci.py`, meaning that a container preloaded with Nix isn't
necessary. Oops 😅

Ubuntu (Nix) container explicitly creates a `buildkite` user to match
the user mapped in when run by BuildKite and Nix is updated to run in
multi-user (daemon) mode via an `ENTRYPOINT` script.

Verified with `docker run -it --rm -u 997:997
gcr.io/bazel-public/ubuntu2204-nix python3` followed by `import certifi`
to validate Python still works, and then `docker run --rm -u 997:997
gcr.io/bazel-public/ubuntu2204-nix /bin/sh -e -c $'cd ~/\n git clone
https://github.com/ConsumingChaos/rules_rust.git\n cd rules_rust\n git
checkout wasm32_cc_info\n cd examples/nix_cross_compiling\n
CARGO_BAZEL_REPIN=true bazel build //:nix_cross_compiling'` to verify
the actual Bazel example target builds.

The `CARGO_BAZEL_REPIN=true` shouldn't be part of the normal run (I
don't think...), but that's something to be fixed in `rules_rust` and
not an issue with the container thankfully 😅