[Bug] Storage information not working on Ubuntu via Docker. #1032
Comments
|
Hello there! The issue looks similar to #944, but we don't know why it is happening. Can you execute the following on your host and in the docker container, and then paste the output? |
|
Hi Maurice, Thanks for looking into this. Below is the requested output. |
|
Thank you! I have created a ticket on the |
|
Thanks Maurice, Will do. |
|
I am having the same issue as well, `docker exec Dash df -kPT |
|
@IllSaft Are you sure you have the same issue? Is your sizes array also empty, like in the snippet posted by @SecOps-7? If so, please follow the linked issue on the |
|
Hello, I rollback packages docker-ce, docker-ce-cli, docker-ce-rootless-extras, and everything is back to normal on dashdot's dashboard. I hope it will help to understand what's happening with the new version of those packages. |
|
@PetitGreg19 Thank you for providing the input! Does that mean that you downgraded docker? Because I setup my home server again like a week ago and dashdot is running fine with what I am assuming are the newest versions of docker. What is your version? |
|
I rolled back to 5.5.1 as that version works best for me. all my drives listed. But it was saying "No mount found." |
At the beginning, I was on Docker 24.0.7 with Dashdot 5.6.1 without any issue. I've updated Dashdot to 5.8.2, still no issue. Few hours later, I've updated my Debian, Docker has been updated from 24.0.7 .to 25.0.0, and the issue about storage has started on Dashdot. Edit : check this -> https://docs.docker.com/engine/release-notes/25.0/ |
|
@IllSaft Are the devices listed showing a correct value for you? Or are the all 0/100%? @PetitGreg19 Thanks for clarifying! I will test the upgrade on my system as well. @SecOps-7 can you check which docker version you are running please? |
|
|
Huh, interesting - can you try if downgrading to 24.x fixes the issues for you? @SecOps-7 |
Downgraded Docker to 24.0.7. No Change. The problem persists. |
|
Upgraded to 25.x and nothing changed for me as well. Weird. |
|
@MauriceNino Sorry for late reply, I installed 2 new 4TB, on previous version it listed correctly, 35Gb/3890Gb, |
@PetitGreg19 You might be on to something. Not sure if it is the cause of issue I'm experiencing since, mine was not working prior to the upgrade to Docker version 25. The Docker release notes state the following:
Note sure if this is of any help. This is the storage driver that is reported in my instance of Docker. |
|
@SecOps-7 I am not sure. I have the same storage driver on my system and dashdot runs fine: Also, I don't know much about the docker storage driver, but if it is about the |
|
Okay, so I thought it might be a good idea to add my GPU information to Dash. So I redeployed it with the "Nvidia" tag and some minor changes to get the GPU to show up and low an behold, the storage works on this build. Not sure what the difference between the nvidia vs the latest build is, but the storage works on nvidia. Here is my docker compose: @MauriceNino I'm happy to collect some more data to help isolate the issue if needed. |
|
sudo docker exec Dashdot yarn cli raw-data --storage Output:const disks = [
{
device: '/dev/nvme0n1',
type: 'NVMe',
name: 'Samsung SSD 980 PRO 1TB ',
vendor: 'Samsung',
size: 1000204886016,
bytesPerSector: null,
totalCylinders: null,
totalHeads: null,
totalSectors: null,
totalTracks: null,
tracksPerCylinder: null,
sectorsPerTrack: null,
firmwareRevision: '',
serialNum: 'S5GXNX0TC19214P',
interfaceType: 'PCIe',
smartStatus: 'unknown',
temperature: null
}
]
const sizes = [
{
fs: 'overlay',
type: 'overlay',
size: 982820896768,
used: 305853267968,
available: 626967543808,
use: 32.79,
mount: '/',
rw: false
},
{
fs: '/dev/nvme0n1p2',
type: 'ext4',
size: 982820896768,
used: 305853267968,
available: 626967543808,
use: 32.79,
mount: '/mnt/host',
rw: true
},
{
fs: 'efivarfs',
type: 'efivarfs',
size: 196608,
used: 117760,
available: 74752,
use: 61.17,
mount: '/mnt/host/sys/firmware/efi/efivars',
rw: false
},
{
fs: '/dev/nvme0n1p1',
type: 'vfat',
size: 535805952,
used: 6369280,
available: 529436672,
use: 1.19,
mount: '/mnt/host/boot/efi',
rw: false
}
]
const blocks = [
{
name: 'nvme0n1',
type: 'disk',
fsType: '',
mount: '',
size: 1000204886016,
physical: 'SSD',
uuid: '',
label: '',
model: 'Samsung SSD 980 PRO 1TB',
serial: 'S5GXNX0TC19214P ',
removable: false,
protocol: 'nvme',
group: '',
device: '/dev/nvme0n1'
},
{
name: 'loop0',
type: 'loop',
fsType: '',
mount: '/mnt/host/snap/bare/5',
size: 4096,
physical: '',
uuid: '',
label: '',
model: '',
serial: '',
removable: false,
protocol: '',
group: ''
},
{
name: 'loop1',
type: 'loop',
fsType: '',
mount: '/mnt/host/snap/certbot-dns-cloudflare/3077',
size: 9715712,
physical: '',
uuid: '',
label: '',
model: '',
serial: '',
removable: false,
protocol: '',
group: ''
},
{
name: 'loop10',
type: 'loop',
fsType: '',
mount: '/mnt/host/snap/firefox/3626',
size: 257945600,
physical: '',
uuid: '',
label: '',
model: '',
serial: '',
removable: false,
protocol: '',
group: ''
},
{
name: 'loop11',
type: 'loop',
fsType: '',
mount: '/mnt/host/snap/gnome-3-38-2004/143',
size: 366682112,
physical: '',
uuid: '',
label: '',
model: '',
serial: '',
removable: false,
protocol: '',
group: ''
},
{
name: 'loop12',
type: 'loop',
fsType: '',
mount: '/mnt/host/snap/gnome-42-2204/120',
size: 509100032,
physical: '',
uuid: '',
label: '',
model: '',
serial: '',
removable: false,
protocol: '',
group: ''
},
{
name: 'loop13',
type: 'loop',
fsType: '',
mount: '/mnt/host/snap/gnome-42-2204/141',
size: 521121792,
physical: '',
uuid: '',
label: '',
model: '',
serial: '',
removable: false,
protocol: '',
group: ''
},
{
name: 'loop14',
type: 'loop',
fsType: '',
mount: '/mnt/host/snap/gtk-common-themes/1535',
size: 96141312,
physical: '',
uuid: '',
label: '',
model: '',
serial: '',
removable: false,
protocol: '',
group: ''
},
{
name: 'loop15',
type: 'loop',
fsType: '',
mount: '/mnt/host/snap/snap-store/959',
size: 12922880,
physical: '',
uuid: '',
label: '',
model: '',
serial: '',
removable: false,
protocol: '',
group: ''
},
{
name: 'loop16',
type: 'loop',
fsType: '',
mount: '/mnt/host/snap/snapd/20290',
size: 42840064,
physical: '',
uuid: '',
label: '',
model: '',
serial: '',
removable: false,
protocol: '',
group: ''
},
{
name: 'loop17',
type: 'loop',
fsType: '',
mount: '/mnt/host/snap/snapd/20671',
size: 42393600,
physical: '',
uuid: '',
label: '',
model: '',
serial: '',
removable: false,
protocol: '',
group: ''
},
{
name: 'loop18',
type: 'loop',
fsType: '',
mount: '/mnt/host/snap/snapd-desktop-integration/83',
size: 462848,
physical: '',
uuid: '',
label: '',
model: '',
serial: '',
removable: false,
protocol: '',
group: ''
},
{
name: 'loop19',
type: 'loop',
fsType: '',
mount: '/mnt/host/snap/firefox/3687',
size: 275263488,
physical: '',
uuid: '',
label: '',
model: '',
serial: '',
removable: false,
protocol: '',
group: ''
},
{
name: 'loop2',
type: 'loop',
fsType: '',
mount: '/mnt/host/snap/canonical-livepatch/246',
size: 10051584,
physical: '',
uuid: '',
label: '',
model: '',
serial: '',
removable: false,
protocol: '',
group: ''
},
{
name: 'loop3',
type: 'loop',
fsType: '',
mount: '/mnt/host/snap/certbot-dns-cloudflare/3182',
size: 9719808,
physical: '',
uuid: '',
label: '',
model: '',
serial: '',
removable: false,
protocol: '',
group: ''
},
{
name: 'loop4',
type: 'loop',
fsType: '',
mount: '/mnt/host/snap/core/16202',
size: 110960640,
physical: '',
uuid: '',
label: '',
model: '',
serial: '',
removable: false,
protocol: '',
group: ''
},
{
name: 'loop5',
type: 'loop',
fsType: '',
mount: '/mnt/host/snap/core20/2015',
size: 66547712,
physical: '',
uuid: '',
label: '',
model: '',
serial: '',
removable: false,
protocol: '',
group: ''
},
{
name: 'loop6',
type: 'loop',
fsType: '',
mount: '/mnt/host/snap/core20/2105',
size: 67014656,
physical: '',
uuid: '',
label: '',
model: '',
serial: '',
removable: false,
protocol: '',
group: ''
},
{
name: 'loop7',
type: 'loop',
fsType: '',
mount: '/mnt/host/snap/core22/1033',
size: 77713408,
physical: '',
uuid: '',
label: '',
model: '',
serial: '',
removable: false,
protocol: '',
group: ''
},
{
name: 'loop8',
type: 'loop',
fsType: '',
mount: '/mnt/host/snap/core22/864',
size: 77492224,
physical: '',
uuid: '',
label: '',
model: '',
serial: '',
removable: false,
protocol: '',
group: ''
},
{
name: 'nvme0n1p1',
type: 'part',
fsType: '',
mount: '/mnt/host/boot/efi',
size: 536870912,
physical: '',
uuid: '',
label: '',
model: '',
serial: '',
removable: false,
protocol: 'nvme',
group: '',
device: '/dev/nvme0n1'
},
{
name: 'nvme0n1p2',
type: 'part',
fsType: '',
mount: '/mnt/host',
size: 999666221056,
physical: '',
uuid: '',
label: '',
model: '',
serial: '',
removable: false,
protocol: 'nvme',
group: '',
device: '/dev/nvme0n1'
}
] |
|
Interesting! Can others with this issue confirm this observation? You don't have to enable GPU to use this package, just try it with your default config please :) |
|
Having the same issue, here's my setup: |
|
@Feramance Can you please try switching out the image for |
|
Just some feedback on the nvidia build. But I'm guessing I should probably open a separate case for this. I found two small bugs.
|
Seems to be working now, though I share the same issues @SecOps-7 mentioned |
|
Same for me, but with one disk correclty displayed and the second one missing. Docker compose: Output of docker exec CONTAINER yarn cli raw-data --storage Output:const disks = [
{
device: '/dev/sda',
type: 'SSD',
name: 'CYX-SSD-S1000 ',
vendor: 'ATA',
size: 256060514304,
bytesPerSector: null,
totalCylinders: null,
totalHeads: null,
totalSectors: null,
totalTracks: null,
tracksPerCylinder: null,
sectorsPerTrack: null,
firmwareRevision: '015',
serialNum: '',
interfaceType: 'SATA',
smartStatus: 'unknown',
temperature: null
},
{
device: '/dev/sdb',
type: 'SSD',
name: 'Samsung SSD 870 ',
vendor: 'Samsung',
size: 4000787030016,
bytesPerSector: null,
totalCylinders: null,
totalHeads: null,
totalSectors: null,
totalTracks: null,
tracksPerCylinder: null,
sectorsPerTrack: null,
firmwareRevision: '2B6Q',
serialNum: '',
interfaceType: 'SATA',
smartStatus: 'unknown',
temperature: null
}
]
const sizes = [
{
fs: 'overlay',
type: 'overlay',
size: 248857907200,
used: 42233233408,
available: 193908805632,
use: 17.88,
mount: '/',
rw: false
},
{
fs: '/dev/mapper/debian--vg-root',
type: 'ext4',
size: 248857907200,
used: 42233233408,
available: 193908805632,
use: 17.88,
mount: '/mnt/host',
rw: true
},
{
fs: '/dev/sda2',
type: 'ext2',
size: 493201408,
used: 114878464,
available: 352738304,
use: 24.57,
mount: '/mnt/host/boot',
rw: false
},
{
fs: '/dev/sda1',
type: 'vfat',
size: 535801856,
used: 6115328,
available: 529686528,
use: 1.14,
mount: '/mnt/host/boot/efi',
rw: false
},
{
fs: '/dev/mapper/dati--vg-dati',
type: 'ext4',
size: 3936853385216,
used: 1779259817984,
available: 1992552947712,
use: 47.17,
mount: '/mnt/host/mnt/dati',
rw: false
}
]
const blocks = [
{
name: 'sda',
type: 'disk',
fsType: '',
mount: '',
size: 256060514304,
physical: 'SSD',
uuid: '',
label: '',
model: 'CYX-SSD-S1000',
serial: '',
removable: false,
protocol: 'sata',
group: '',
device: '/dev/sda'
},
{
name: 'sdb',
type: 'disk',
fsType: 'LVM2_member',
mount: '',
size: 4000787030016,
physical: 'SSD',
uuid: '5T6A2s-BxVh-BTLu-HyX3-ixxQ-NKQU-IV0ufC',
label: '',
model: 'Samsung SSD 870',
serial: '',
removable: false,
protocol: 'sata',
group: '',
device: '/dev/sdb'
},
{
name: 'sda1',
type: 'part',
fsType: 'vfat',
mount: '/mnt/host/boot/efi',
size: 536870912,
physical: '',
uuid: 'C15B-0F2F',
label: '',
model: '',
serial: '',
removable: false,
protocol: '',
group: '',
device: '/dev/sda'
},
{
name: 'sda2',
type: 'part',
fsType: 'ext2',
mount: '/mnt/host/boot',
size: 511705088,
physical: '',
uuid: 'b1271237-89d9-4040-994d-f0c06424e67f',
label: '',
model: '',
serial: '',
removable: false,
protocol: '',
group: '',
device: '/dev/sda'
},
{
name: 'sda3',
type: 'part',
fsType: 'LVM2_member',
mount: '',
size: 255010537472,
physical: '',
uuid: 'NUaVGh-81PZ-RMae-gTm9-9arw-uXHF-eZvIRV',
label: '',
model: '',
serial: '',
removable: false,
protocol: '',
group: '',
device: '/dev/sda'
}
]Relevant part of the output: |
|
Hi everyone, I had a similar problem until today. After upgrade packages & reboot I have correct disk graph. my storage measurement was [-1,-1] but now measurement array has values uname -a docker versiondnf history infocontainer logsdocker servicescreens
@SecOps-7 could you check problem after upgrade your Ubuntu packages? |
|
@djwinston Thanks for the update. Much appreciated. I can confirm that after updating my Ubuntu packages and rebooting, it started working. |
|
Spoke to soon. Just got another few updates from Ubuntu and its broken again. |
|
@SecOps-7 Could you provide log of upgraded packages? last two upgrades. We need to investigate it. I'll aso try upgrade when next update available |
|
@djwinston Below are the packages that where updated today. Issue was fixed after these docker updates were installed: These Ubuntu updates then broke it again: |
|
@SecOps-7 so if you compare our update logs, the only difference is in the kernel. But it won't help. check this sudo docker context lsand try up compose with your GID UID ids environment:
...
UID: _your uid_
GID: _your gid_ |
|
@djwinston I get the exact same result as you. |
|
I think the problem is that if you are using LVM or crypt there is no way for a docker app to see what is inside, e.g. this is difference: Docker docker exec dash lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 45M 1 loop /mnt/host/snap/certbot/3566
loop1 7:1 0 45.2M 1 loop /mnt/host/snap/certbot/3643
loop2 7:2 0 105.8M 1 loop /mnt/host/snap/core/16202
loop3 7:3 0 105.4M 1 loop /mnt/host/snap/core/16574
loop4 7:4 0 55.7M 1 loop /mnt/host/snap/core18/2796
loop5 7:5 0 55.7M 1 loop /mnt/host/snap/core18/2812
loop6 7:6 0 63.9M 1 loop /mnt/host/snap/core20/2105
loop7 7:7 0 63.9M 1 loop /mnt/host/snap/core20/2182
loop8 7:8 0 91.8M 1 loop /mnt/host/snap/lxd/23991
loop9 7:9 0 91.8M 1 loop /mnt/host/snap/lxd/24061
sda 8:0 0 5.5T 0 disk
└─sda1 8:1 0 5.5T 0 part
└─md0 9:0 0 5.5T 0 raid1
sdb 8:16 0 5.5T 0 disk
└─sdb1 8:17 0 5.5T 0 part
└─md0 9:0 0 5.5T 0 raid1
sdc 8:32 0 931.5G 0 disk
sdd 8:48 0 476.9G 0 disk
├─sdd1 8:49 0 512M 0 part /mnt/host/boot/efi
├─sdd2 8:50 0 1G 0 part /mnt/host/boot
└─sdd3 8:51 0 475.4G 0 part System lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 45M 1 loop /snap/certbot/3566
loop1 7:1 0 45.2M 1 loop /snap/certbot/3643
loop2 7:2 0 105.8M 1 loop /snap/core/16202
loop3 7:3 0 105.4M 1 loop /snap/core/16574
loop4 7:4 0 55.7M 1 loop /snap/core18/2796
loop5 7:5 0 55.7M 1 loop /snap/core18/2812
loop6 7:6 0 63.9M 1 loop /snap/core20/2105
loop7 7:7 0 63.9M 1 loop /snap/core20/2182
loop8 7:8 0 91.8M 1 loop /snap/lxd/23991
loop9 7:9 0 91.8M 1 loop /snap/lxd/24061
sda 8:0 0 5.5T 0 disk
`-sda1 8:1 0 5.5T 0 part
`-md0 9:0 0 5.5T 0 raid1
`-raid 253:5 0 5.5T 0 crypt
`-raid--vg-data--lv 253:6 0 5.5T 0 lvm /var/nextcloud
sdb 8:16 0 5.5T 0 disk
`-sdb1 8:17 0 5.5T 0 part
`-md0 9:0 0 5.5T 0 raid1
`-raid 253:5 0 5.5T 0 crypt
`-raid--vg-data--lv 253:6 0 5.5T 0 lvm /var/nextcloud
sdc 8:32 0 931.5G 0 disk
`-SMALL 253:3 0 931.5G 0 crypt
`-vg--smallraid-lv--smallraid 253:4 0 931G 0 lvm /mnt/smallraid
sdd 8:48 0 476.9G 0 disk
|-sdd1 8:49 0 512M 0 part /boot/efi
|-sdd2 8:50 0 1G 0 part /boot
`-sdd3 8:51 0 475.4G 0 part
|-ubuntu--vg-ubuntu--lv 253:0 0 150G 0 lvm /
|-ubuntu--vg-nextcoud_previews_lv 253:1 0 150G 0 lvm /mnt/raid/nextcloud/data/appdata
`-ubuntu--vg-docker_lv 253:2 0 50G 0 lvm |
|
I also came across this issue today, but only when I moved from using The only real difference I could come across is that bash was the shell env for the |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description of the bug
Good day,
Firstly, thank you for developing such a useful and beautiful resource dashboard. Love your work.
Currently storage information is not being displayed correctly on Ubuntu via Docker.
Below are my setup details:
Hardware:
Intel NUC 13 Core i5 (NUC13ANKi5)
Storage setup:
Samsung 980 Pro M.2 NVMe SSD
Config:
Running Latest Version of Dashdot
Specific hosting form:
Docker running on Ubuntu 22.04.3 LTS x86_64
Anything you deem important:
How to reproduce
Relevant log output
Info output of dashdot cli
What browsers are you seeing the problem on?
Firefox
Where is your instance running?
Linux Server
Additional context
docker exec CONTAINER yarn cli raw-data --storage output
Output:
The text was updated successfully, but these errors were encountered: