-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CI flake: secret file is not leaked into image #13417
Labels
flakes
Flakes from Continuous Integration
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
remote
Problem is in podman-remote
Comments
edsantiago
added
flakes
Flakes from Continuous Integration
remote
Problem is in podman-remote
labels
Mar 3, 2022
@ashley-cui please take a look |
Still flaking; reopening Podman build [It] podman build with a secret from file and verify if secret file is not leaked into image
|
@ashley-cui can you take a look? |
Ahh! Forgot about this, taking another look now |
github-actions
bot
added
the
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
label
Sep 20, 2023
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
flakes
Flakes from Continuous Integration
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
remote
Problem is in podman-remote
Pretty rare flake:
(formatted for legibility).
This is ginkgo, so my hunch is that multiple secrets-related tests are all running at once. One super-simple fix might be to move
test/e2e/build/Dockerfile.with-secret-verify-leak
into a new subdirectory,test/e2e/build/secret-verify-leak
. It should be very easy to do this and see if the flake goes away. But it's also possible that this is a real bug.Seems to be remote only.
Podman build [It] podman build with a secret from file and verify if secret file is not leaked into image
The text was updated successfully, but these errors were encountered: