Paul Colomiets

This error means that container version changes during the build of that container. At a glance, I don't see any obvious conflicts here. But maybe it's because of things you've...

> Is that correct that I !Depend on Cargo.toml and src in container, that builds a Rust project and puts the binary to /usr/local/bin in the container?.. Yes, it looks...

Well, these are offending lines: ``` - !Sh | cd pavetta cargo build --target-dir /work/.vagga-ws/target/pavetta - !Copy source: /work/.vagga-ws/target/pavetta/debug/pavetta path: /usr/local/bin/pavetta ``` Because `source` in `!Copy` are in `/work`, they...

Well, thank you for finding this out! It's really a bug, but not trivial to fix: 1. The bug essentially is that SubConfig doesn't expose container it depends on, like...

Extra thoughts: It became easier to spot when I enabled debug log (`RUST_LOG=info vagga pavette`), there was no container `pavetta-redist` built before the `pavetta-sdk-custom` If we are to fix the...

Not sure I understand the issue. If you're building from source we download busybox and cache it. When you're downloaded binary package it already contains supported version of busybox. But...

Yes sounds good (I think overlayfs didn't work in unprivileged mode in 2017 when issue was created :) ). And I think it's fine to put upper dir in container's...

Actually, we use `RegexSet` for the domain routing since f89036e. Should fix the same issue for path routing, though.

It's unclear whether we want to forward it in metadata or as a header.

Okay the first two things to do are: 1. Expose metric for the size of the backend queue 2. Cancel dropped (timed out) connections (to keep queue minimal)