As the issue title says, tarball writes the whole directory into the tarball, ignoring any .dockerignore files present. This is a problem because a) the build context is not the same as a cli invocation of docker build ... and hence may be surprising and b) in an async context tarball blocks the async runtime while it reads the filesystem and if you have a lot of .dockerignored files (e.g a node_modules directory) then this can interfere with other async operations.

Sems that Docker 24 add some new TTY stream that containers-api crate refused to use and assert the execution:

let chunk = match header_bytes[0] {
        0 => TtyChunk::StdIn(data),
        1 => TtyChunk::StdOut(data),
        2 => TtyChunk::StdErr(data),
        n => panic!("invalid stream number from podman daemon: '{n}'"),
    };

But i get this:

thread '<unnamed>' panicked at 'invalid stream number from podman daemon: '3'', /home/luis/.cargo/registry/src/index.crates.io-6f17d22bba15001f/containers-api-0.9.0/src/conn/tty.rs:82:14