dashdot: [Bug] Storage info showing 0% Used

Description of the bug

Storage info shows 0% used for two external drives that are mounted correctly on the host system.

host system df command shows the correct usage, but docker exec CONTAINERNAME df does not list those drives.

image

How to reproduce

No response

Relevant log output

~$ docker exec dashdot df

Filesystem           1K-blocks      Used Available Use% Mounted on
overlay              243520884  10157440 220920412   4% /
tmpfs                    65536         0     65536   0% /dev
shm                      65536         0     65536   0% /dev/shm
/dev/sda2            243520884  10157440 220920412   4% /etc/os-release
/dev/sda2            243520884  10157440 220920412   4% /etc/resolv.conf
/dev/sda2            243520884  10157440 220920412   4% /etc/hostname
/dev/sda2            243520884  10157440 220920412   4% /etc/hosts
~$ df
Filesystem       1K-blocks       Used   Available Use% Mounted on
udev               4007980          0     4007980   0% /dev
tmpfs               804856       2984      801872   1% /run
/dev/sda2        243520884   10157532   220920320   5% /
tmpfs              4024276          4     4024272   1% /dev/shm
tmpfs                 5120          0        5120   0% /run/lock
/dev/sdb       15501595160 4703826544 10016458256  32% /media/seagateUSB
/dev/sda1           523244       3804      519440   1% /boot/efi
/dev/sdc       15501595160         28 14720284772   1% /media/seagateUSBBackup
tmpfs               804852          0      804852   0% /run/user/1000

Info output of dashdot cli

~$ docker exec dashdot yarn cli info
yarn run v1.22.19
$ node dist/apps/cli/main.js info
INFO
=========
Yarn: 1.22.19
Node: v18.5.0
Dash: 4.3.2

Cwd: /app
Hash: ca180c09161e3fc1e0cc154e2f379359528877d1
In Docker: true
In Podman: false
In Docker (env): true
Done in 0.38s.

What browsers are you seeing the problem on?

Chrome

Where is your instance running?

Linux Server

Additional context

No response

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Comments: 15 (7 by maintainers)

Commits related to this issue

Most upvoted comments

@MauriceNino Thank you, it’s working! πŸ˜ƒ

πŸŽ‰ This issue has been resolved in version 4.3.4

Please check the changelog for more details.