-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
unlinkat directory not empty on commit (rootless) #23023
Comments
please provide more information on the environment. I see only one mapping is available. How was the user created? Is it a nested container?
|
Hi @giuseppe, Here is the output of podman info:
|
I see the message:
In what environment are you running that command? Is it a nested container? Directly on the host? Also this is the issue tracker for the upstream development, so please try with a newer version of Podman to see if the issue still persists |
We already tried with the latest version and still the same issue. In regards to the environment, this is a k8s pod running rootless docker daemon. |
I've tried to reproduce a similar environment, running nested podman but I am not able to reproduce it yet. Could you try to run podman inside podman (so no Docker involved) and see if that behaves in the same way for you? You can just use the Could you share your |
Issue Description
Getting the following error "randomly" when trying to build an image using the following command -> podman build --isolation chroot -t .
17:11:18 COMMIT foo:latest 17:11:18 --> 4434cee3fd5 17:11:18 Successfully tagged localhost/foo:latest 17:11:32 time="2024-06-14T21:11:30Z" level=error msg="error deleting build container \"dffdfc25f7f9f183eaca0c83ad95cd42daa5fbe0f33ec56cc8c525f3b0d5a98f\": 1 error occurred:\n\t* unlinkat /var/lib/containers/storage/vfs/dir/2157acd33ff63d42f27f2b14276c62bd0dea9d6d856849bad18da2220dfdf9e9: directory not empty\n\n\n" 17:11:32 Error: unlinkat /var/lib/containers/storage/vfs/dir/2157acd33ff63d42f27f2b14276c62bd0dea9d6d856849bad18da2220dfdf9e9: directory not empty
Any ideas/things to try etc ?
Steps to reproduce the issue
Unfortunately, the issue cannot be reproduced reliably and as stated in the description, it seems to occur randomly.
Describe the results you received
See description
Describe the results you expected
No error and a successful image build.
podman info output
Podman in a container
Yes
Privileged Or Rootless
Rootless
Upstream Latest Release
No
Additional environment details
Runs on an GCP compute engine instance
Additional information
Additional information like issue happens only occasionally or issue happens with a particular architecture or on a particular setting
The text was updated successfully, but these errors were encountered: