Paul, thanks for reply.
Agree, it may be related with the file system.
I use this workaround to add `--local` and `-x` flag for `df` to avoid the
wrong calculation. I got the workaround from
https://github.com/moby/moby/issues/42823#issuecomment-913584814.
Best regards
Paco
在 2021/9/8 下午2
On 9/8/21 12:02 AM, Paco Xu wrote:
I use this workaround to add `--local` and `-x` flag for `df` to avoid the
wrong calculation. I got the workaround
fromhttps://github.com/moby/moby/issues/42823#issuecomment-913584814.
Thanks for following up; closing the bug report.
It sounds like df is reporting disk usage for the file system you're
running your docker instance atop. In that case, there may be other uses
of the file system, aside from the docker instance, which means df is
reporting the correct numbers (and du is, too).
The problem, if it is a problem, i
On 06/09/2021 11:33 am, Paco Xu wrote:
Hi,
I am not quite familiar with the bug report process of `DF` or os.
The Problem
- DF shows incorrect disk usage which include disk usage of a mounted path
The Scenario
We run a registry with docker and the data dir is mounted from NFS or local
Hi,
I am not quite familiar with the bug report process of `DF` or os.
The Problem
- DF shows incorrect disk usage which include disk usage of a mounted path
The Scenario
We run a registry with docker and the data dir is mounted from NFS or local
disk. The docker is using device-mapper.
