buildx VS crates.io-index

This is great! I’ve been waiting a long time for this and it seems like more debug features are in the pipeline too: https://github.com/docker/buildx/issues/1104

Docs: https://docs.docker.com/engine/reference/commandline/buildx_...

Container engine: Docker v23.0.4 | Buildx v0.10.4

ARCH=amd64 # change to 'arm64' for M1 VERSION=v0.10.4 curl -LO https://github.com/docker/buildx/releases/download/${VERSION}/buildx-${VERSION}.darwin-${ARCH} mkdir -p ~/.docker/cli-plugins mv buildx-${VERSION}.darwin-${ARCH} ~/.docker/cli-plugins/docker-buildx chmod +x ~/.docker/cli-plugins/docker-buildx docker buildx version # verify installation

wget -O /tmp/docker/cli-plugins/docker-buildx https://github.com/docker/buildx/releases/tag/v0.10.4/buildx-v0.10.4.linux-amd64

Your particular one looks somewhat like https://github.com/docker/buildx/issues/1595.

Now, we have examples of the actual definitions for a single application’s docker container. Notice that we set the contexts key here which references the dependency targets we just defined. You can basically think of this like the depends_on block if you’ve used Terraform before. The args key let’s us populate the ARG variables in the Dockerfile. This is what is ultimately different between each of the containers. In the future, the buildx team might support using for_each loops like in Terraform but for now each block will have a bit of duplication.

Now as bonus we i will add how to use this techniques to build a multi arch build container. Maybe you have the same application but you need to run it in arm or riscv architecture. For this we can use the buildx plugin from docker https://github.com/docker/buildx.

Third step is docker/setup-buildx-action configures buildx, which is a Docker CLI plugin that provides enhanced build capabilities.

That's already prevented by the checksum which is present for all crate versions in the registry index, which is set in stone on publish and verified by cargo on download. See e.g. https://github.com/rust-lang/crates.io-index/blob/74f1b1e064...

Why is the crates.io registry Git repository structured the way it is? https://github.com/rust-lang/crates.io-index

# $HOME/.cargo/config.toml [...] [registry] default = "gitea" [registries.crates] index = "https://github.com/rust-lang/crates.io-index.git" [registries.gitea] index = "https://gitea.localhost.local/user/_cargo-index.get" [...]

[[package]] name = "cbindgen" version = "0.24.3" source = "registry+https://github.com/rust-lang/crates.io-index" checksum = "a6358dedf60f4d9b8db43ad187391afe959746101346fe51bb978126bec61dfb" dependencies = [ "clap 3.2.23", "heck", "indexmap", "log", "proc-macro2", "quote", "serde", "serde_json", "syn 1.0.109", "tempfile", "toml 0.5.11", ]

$ cargo upgrade --dry-run --compatible ignore --incompatible allow --pinned ignore --verbose 2>&1 Updating 'https://github.com/rust-lang/crates.io-index' index Checking foo's dependencies name old req compatible latest new req note ==== ======= ========== ====== ======= ==== axum 0.6.11 0.6.15 0.6.15 0.6.11 compatible base64 0.20.0 0.20.0 0.21.0 0.21.0 ...

I am getting: spurious network error (2 tries remaining): unexpected http status code: 503; class=Http Caused by: failed to fetch https://github.com/rust-lang/crates.io-index

https://github.com/rust-lang/crates.io-index contains the entire crates.io index with the names of all crates and their dependencies. grep or ripgrep over that should do the job.

[[package]] name = "spade" version = "2.1.0" source = "registry+https://github.com/rust-lang/crates.io-index" checksum = "1190e0e8f4eb17fc3dbb2d20e1142676e56aaac3daede39f64a3302d687b80f3" dependencies = [ "num-traits", "optional", "robust 0.2.3 (registry+https://github.com/rust-lang/crates.io-index)", "smallvec", ]

Caused by: process didn't exit successfully: git fetch --force --update-head-ok 'https://github.com/rust-lang/crates.io-index' '+HEAD:refs/remotes/origin/HEAD' (exit status: 128) --- stderr error: 2747 bytes of body are still expected fetch-pack: unexpected disconnect while reading sideband packet fatal: early EOF fatal: fetch-pack: invalid index-pack output