Rust 1.47.0 is causing CI to fail

[zmrow]

Related to bottlerocket-os/bottlerocket-sdk#36

Platform I'm building on:
GitHub Actions

What I expected to happen:
Bottlerocket to build successfully in CI

What actually happened:
In CI, the build fails with errors similar to:

2020-10-09T18:42:05.0204440Z   Error response from daemon: Conflict. The container name "/buildsys-pkg-glibc-x86_64-2fe95a9c2d67" is already in use by container "e578bf40fc498b9cbe4b13b1a866d023c702cce35d44e27103293c5de852f2fc". You have to remove (or rename) that container to be able to reuse that name.

How to reproduce the problem:
Use Rust 1.47.0 and attempt to build Bottlerocket via cargo make

I'm able to build Bottlerocket successfully with Rust 1.46.0

[bcressey]

We're seeing concurrent invocations of build scripts for workspace crates that are dependencies of multiple crates. This doesn't always result in an error, but even in the best case it means duplicated work.

It's most obvious in a clean workspace where we can see multiple glibc builds kicked off right away:

❯ cargo make -e BUILDSYS_VARIANT=aws-dev build-packages
[cargo-make] INFO - cargo make 0.32.3
[cargo-make] INFO - Build File: Makefile.toml
[cargo-make] INFO - Task: build-packages
[cargo-make] INFO - Profile: development
[cargo-make] INFO - Running Task: build-packages
   Compiling glibc v0.1.0 (/home/fedora/bottlerocket/packages/glibc)
   Compiling kernel v0.1.0 (/home/fedora/bottlerocket/packages/kernel)
   Compiling libstd-rust v0.1.0 (/home/fedora/bottlerocket/packages/libstd-rust)
^C  Building [==>                                                     ] 18/265: glibc(build), kernel(build), glibc(build), libstd-rust(build)

It also happens with libmnl which many of the networking tools and libraries depend on.

[bcressey]

I bisected this back to rust-lang/cargo@dc4b695 which describes some possible workarounds.