From 9ce3c0a87a6d7da45e71719b2ceb6d6abb0433fe Mon Sep 17 00:00:00 2001 From: Ashley Cui Date: Tue, 8 Mar 2022 09:45:48 -0500 Subject: Move secret-verify-leak containerfile into its own Directory Secret-verify-leak is causing flakes, when running in parallel tests. This is because remote secrets are copied into the context directory to send to the API server, and secret-verify-leak is doing a COPY * and then checking if the temporary secret file ends up in the container or not. Since all the temporary files are prefixed with "podman-build-secret", this test checks if podman-build-secret is in the image. However, when run in parallel with other tests, other temporary podman-build-secrets might be in the context dir. Moving secret-verify-leak into its own directory makes sure that the context dir is used only by this one test. Also renamed Dockerfile -> Containerfile and cleaned up unused Containerfiles. Signed-off-by: Ashley Cui --- .../e2e/build/secret-verify-leak/Containerfile.with-secret-verify-leak | 3 +++ 1 file changed, 3 insertions(+) create mode 100644 test/e2e/build/secret-verify-leak/Containerfile.with-secret-verify-leak (limited to 'test/e2e/build/secret-verify-leak/Containerfile.with-secret-verify-leak') diff --git a/test/e2e/build/secret-verify-leak/Containerfile.with-secret-verify-leak b/test/e2e/build/secret-verify-leak/Containerfile.with-secret-verify-leak new file mode 100644 index 000000000..0957ac6a6 --- /dev/null +++ b/test/e2e/build/secret-verify-leak/Containerfile.with-secret-verify-leak @@ -0,0 +1,3 @@ +FROM alpine +COPY * / +RUN --mount=type=secret,id=mysecret cat /run/secrets/mysecret -- cgit v1.2.3-54-g00ecf