Thomas Eizinger

Perhaps it is a lost battle until Nix takes over the world.

We will be removing all images from this library, see https://github.com/testcontainers/testcontainers-rs/issues/471.

> looks like some API changes 😿 Less allocations when sending data (click on "Files changed"): https://github.com/quinn-rs/quinn/compare/88f48b0179f358cea0b76fc550e629007bfc957d...1e547588e8b3d86cfd6450cad73f480e1232c351#diff-a4c3723adabe724e50ad02cdb86f1a32242ee842f2991b7dad5152265bf955e3 This will require some refactoring because we currently rely on being able to...

It also appears that we can no longer pass a slice of messages to send and now need to queue each message separately. Looking at the old implementation, it also...

We build containers for our tests using a buildscript: https://github.com/testcontainers/testcontainers-rs/blob/dev/testimages/build.rs You should be able to do something similar for your app. The feature is indeed missing but I don't have...

> The motivation here is to allow the crate's http client to talk to the daemon http API over unix sockets and windows named pipes, not just TCP. This currently...

> This PR includes a symlink to the LICENSEs and README files in the > crate, which should make `cargo publish` include these files when > publishing to crates.io. Can...

Are you running your tests concurrently? I wouldn't be surprised if there are race conditions within the `docker` CLI. I ran into some myself. You can try using the experimental...

> Ah, so if this is a known issue then is the way to resolve this just to add some documentation to recommend switching to the experimental HTTP client method...

> I am unable to find an equivalent to this functionality in the Rust crate. How can one do this? It is not supported at the moment. I am not...