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
Unable to create new file after few days in my container #33497
Comments
Do you need more information ? I'll have to restart the container :/ EDIT: I've added some information. |
|
Maybe it's something fixed in kernel 4.8 or 4.10 ? |
I don't know of any issues which would cause this. After you restart are you able to reproduce getting the container into this state? Also can you list the directory contents for each of the files which complained about the directory not existing? Is there any process in the container that could be responsible for deleting files? Also look at the mount and check whether all the lower directories still exist on the host. |
@dmcgowan yes, I'm able to reproduce the state (sometimes it's few days, sometime it's a week). The directories are not empty (except for /tmp), there is nothing deleting files (this issues appends in different containers on different hosts). All directories still exist on the host.
|
I do see @goldyfruit Do you know if this occurs after the daemon was restarted? |
@thaJeztah I don't remember but I just tested to restart the docker deamon on an another host and I don't have any issue. You suggestion is not a bad one, how can I confirm that the filesystem are not remounted ? Thanks for your time guys ! |
@thaJeztah I'll turned off the Any other thoughts guys ? |
No other thoughts at this point, but keep us posted if disabling live-restore makes a difference |
I turned off the |
So, sadly |
We just experience this on an Azure box and its driving us crazy. @goldyfruit where you able to fix this? |
@argiris-mat Don't have this issue anymore since the Docker 18.0X versions. |
Hi guys.
After few days, some of my containers are not able to write in some directories anymore.
Example:
The application needs to create sockets but it can't and it fails with a trace like that:
If I restart the container, it's works. Make me think something related to
overlayfs
and some layers issue.Docker version:
Please find a paste of
# strace -ff docker exec neutron_vpnaas_agent touch /tmp/toto
: https://paste.api-zulu.com/sehegemaye.vbsThe text was updated successfully, but these errors were encountered: