Install rustup and cargo in CI and prod build images#64535
Install rustup and cargo in CI and prod build images#64535potiuk wants to merge 9 commits intoapache:mainfrom
Conversation
|
This one should fix a nasty race condition that @radu-gheorghe had in #63988 where |
4dbceaf to
9eed782
Compare
|
This will need fix from #64547 likely |
9eed782 to
b028794
Compare
|
This one also is quite a bit too long. I will add the same retry for installation in regular image build as in Low Deps to fix the issue cc: @radu-gheorghe |
|
Closing in favour of #64588 |
b028794 to
d4d0500
Compare
|
OK. I restore that one, add longer timeout - this timeout is not really going to impact most of the builds, that will use local or remote cache. We should rebase #63988 and it should solve all the issues with rustup parallel installs |
Download the rustup-init binary directly and verify its SHA256 checksum before execution, instead of piping the shell installer script through sh.
Pin rustup-init to version 1.29.0 with hardcoded SHA256 checksums for amd64 and arm64, matching the existing cosign verification pattern. This prevents a compromised server from serving a tampered binary with a matching checksum.
|
Added extra verification / crypto/hash check of the init script. I will also - as next PR update "upgrede important version" prek to bump this one - with cooldown - when new version is released. |
|
Re-created it here #64725 as the rebase got mixed up with Vespa changes. |
|
cc: @bugraoz93 |
Add rustup/cargo installation to the CI image and production build image so that
Python packages with Rust extensions can be compiled from source during image builds.
install_rustup()function toinstall_os_dependencies.shRUSTUP_HOME,CARGO_HOMEenv vars and add cargo toPATHin both Dockerfiles/root/.cargo/binPATH entry in Dockerfile.ciWas generative AI tooling used to co-author this PR?
Generated-by: Claude Code (Claude Opus 4.6) following the guidelines