-
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
APIv2: DELETE libpod/containers/foo?force=true: unlinkat: directory not empty #7535
Comments
Also seen here https://cirrus-ci.com/task/6597748277379072 in #6811 |
I've been poking around in the code and couldn't find anything suspicious in the code that would explain the flake. However, local podman will evict containers in case of Could it be that the |
My first suspicion would be that the unmount has not completely finished. If we add a 5-second sleep between them, that would help confirm the race. |
This one is quickly becoming the number-one flake 259 [25-containersMore] DELETE libpod/containers/foo?force=true : status
260 [25-containersMore] DELETE libpod/containers/foo?force=true: 204 status returns no output
|
Fixes containers#7535 Signed-off-by: Jhon Honce <[email protected]>
Fixes containers#7535 Signed-off-by: Jhon Honce <[email protected]>
Fixes containers#7535 Signed-off-by: Jhon Honce <[email protected]>
Probable flake; filing so we can track it. In API tests:
Source: apiv2_test in #7534
Am assuming it's a flake, since I didn't touch any of this code. Will restart failing test.
The text was updated successfully, but these errors were encountered: