From 3537f8e1d174f2ce422c9024a9e0d6df87ad9207 Mon Sep 17 00:00:00 2001 From: Matthias Beyer Date: Mon, 12 Apr 2021 18:43:04 +0200 Subject: Filter out the /outputs/ directory The issue here is that we copy all build results (packages) in the container to /outputs and then butido uses that directory to fetch the outputs of the build. But, because how the docker API works, we get a TAR stream from docker that _contains_ the /outputs directory. But of course, we don't want that. Until now, that was no issue. But it has become one now that we start adopting butido for our real-world scenarios. This patch adds filtering out that /outputs portion of the pathes from the tar archive when writing all the things to disc. Signed-off-by: Matthias Beyer Tested-by: Matthias Beyer --- doc/containers.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'doc/containers.md') diff --git a/doc/containers.md b/doc/containers.md index cbb62a0..52f4b4a 100644 --- a/doc/containers.md +++ b/doc/containers.md @@ -15,7 +15,7 @@ on. Those are listed here. 1. Dependencies are named `/inputs/-.pkg` inside the container 2. Sources are named `/inputs/src-.source` -3. Outputs are expected to be named `/outputs/-.pkg` +3. Outputs are expected to be written to the `/outputs` directory The reason for the names lies in the artifact parsing mechanism. If the package is named differently, the artifact parsing mechanism is not able -- cgit v1.2.3