Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#65032 - [docker] (overlay2) mounts not being unmounted when stopping docker
Attached to Project:
Community Packages
Opened by Lukas (luman) - Friday, 03 January 2020, 16:40 GMT
Last edited by Sébastien Luttringer (seblu) - Wednesday, 20 May 2020, 14:58 GMT
Opened by Lukas (luman) - Friday, 03 January 2020, 16:40 GMT
Last edited by Sébastien Luttringer (seblu) - Wednesday, 20 May 2020, 14:58 GMT
|
DetailsDescription:
Running a server with multiple docker containers deployed by docker-compose. After some days/weeks/months, I want to reboot the server. Before rebooting, I am trying to cleanly stop and unmount everything. After stopping docker, there are some overlay2 mountpoints left over which prevent to unmount the underlying filesystem which eventually lets the whole server hang on shutdown. How can I figure out where the issue is and/or whether this is a bug? Additional info: * package version(s) community/docker 1:19.03.5-1 [installed] Steps to reproduce: Not sure if that helps, because it does not seem to be always reproducible: 1) boot server 2) decrypt volumes 3) mount fs 4) start docker 5) start containers 6) wait 7) stop docker 8) mount | grep overlay2 umount /mnt/data fails because there are left over mounts in /mnt/data/docker workaround: for m in `mount | grep overlay | awk '{ print $3 }'`; do umount $m;done for m in `mount | grep nsfs | awk '{ print $3 }'`; do umount $m;done for m in `mount | grep shm | awk '{ print $3 }'`; do umount $m;done followed by: umount /mnt/data |
This task depends upon
Closed by Sébastien Luttringer (seblu)
Wednesday, 20 May 2020, 14:58 GMT
Reason for closing: Not a bug
Wednesday, 20 May 2020, 14:58 GMT
Reason for closing: Not a bug
https://github.com/moby/moby/issues/40344
Issues and fixes are better troubleshooted upstream, where they known better how the software work, and they decide the best way to address them. Even if ultimately the solution is to update the user manual.
An upstream maintainer was *very* responsive and answered you quickly, asking for more information.
This was left unanswered.
I kept this report open, to track and eventually early patch the software if something emerge from the upstream issue.
Since your last message here, 4 new minor versions of docker was released and packaged.
As the issue was stalled upstream, I closed as No Answer.
Let's close this for now. I also think, it is quite likely that one of the applications misbehaved and not docker itself.
Thanks for helping!