On 2/7/2020 at 2:32 AM, G@n0nD0rf said:

Is it possible to scan on disc level? I have enabled disc shares but I can't see them in QDirStat.

You can change the Docker config so that /storage points to simply /mnt (vice /mnt/user/) and each disk will show up as a Directory to open. However, you won't see "/mnt/user" (not sure why).

 

Hope this will help folks.

KJ

Hi,

Thank you for the application.

I need to do some cleaning on my disk and it's a great help.

But I have permission problems when I want to delete something. Is there a way to fix this ?

I didn't change User ID: 99 nor Group ID: 100, the default value in Docker template... maybe here ?

3 hours ago, zarkoff said:

Hi,

Thank you for the application.

I need to do some cleaning on my disk and it's a great help.

But I have permission problems when I want to delete something. Is there a way to fix this ?

I didn't change User ID: 99 nor Group ID: 100, the default value in Docker template... maybe here ?

By default the volume mapping is read-only.  To change it, edit the containers settings, toggle the Advanced View (at the upper right), click the Edit button next to the "Storage" setting and change the Access Mode to Read/Write.

@Djoss Ok many thanks !

I recently changed my cache from BTRFS to XFS, and now I can't seem to scan the root of /mnt/cache in this app any longer.  I get a greyed out list of folders, perhaps a permissions issue?  I can scan them individually, but not at the root level of the cache drive(s):

 

Did you check the permissions of this folder ?

 

ls -ld /mnt/cache

 

Edited June 29, 20233 yr by Djoss

Thanks for creating this container.  Is there a way to adjust how the container runs so that it can access folders owned by root?  Right now, any folders owned by root are highlighted in red and cannot be analyzed.  I tried running in privileged mode and also changing the PUID & PGID to zero, but neither helped.  Thanks!

 

Thank you.  

In container settings, the fields "User ID" and "Group ID" define the user under which the application will run.

Is there any way to increase the amount of files the list of largest files is? It seems to be limited to 200 right now, can you increase it?

I want to request 2 features for it, as i for one keep it open at all times to not have to rescan all the data every time it restarts from either server restart, or other task requiring array to be stopped.

1: A session save/restore function, where it will write all the files it has found per sector to a text file on the ram, And whenever it's getting the shutdown command if we restart server/stop docker, first command it will self issue to itself, is write that "text file" from ram onto a text file in it's appdata folder, so it can load it up again and resume from where it was last time. 

And as it knows where the existing files were prior to restart/docker shutdown, it will scan any other sector that contains files it hasn't logged yet.

That way we can save half a day++ on every rescan.

1: Auto scan and add new files/autodetect if a file has been deleted to the list whenever it detects such activity.

There is already a way to save/restore the result of a scan, but I guess this is not what you are looking for. Since this container only packages QDirStat, I would suggest that you also provide your requests at https://github.com/shundhammer/qdirstat.

Latest Qdirstat docker is showing the wrong folder content while scanning. I click on data, but it shows "documents" for example.

This container is suddenly not working for me (after many years). I get a black screen when I load the WebUI, and I see this in the logs:

[xvnc ] Underlying X server release 12101021

[xvnc ] MESA-LOADER: failed to open iris: Error loading shared library /usr/lib/xorg/modules/dri/iris_dri.so: No such file or directory (search paths /usr/lib/xorg/modules/dri, suffix _dri)

[xvnc ] MESA-LOADER: failed to open kms_swrast: Error loading shared library /usr/lib/xorg/modules/dri/kms_swrast_dri.so: No such file or directory (search paths /usr/lib/xorg/modules/dri, suffix _dri)

[xvnc ] MESA-LOADER: failed to open swrast: Error loading shared library /usr/lib/xorg/modules/dri/swrast_dri.so: No such file or directory (search paths /usr/lib/xorg/modules/dri, suffix _dri)

[xvnc ] MESA-LOADER: failed to open iris: Error loading shared library /usr/lib/xorg/modules/dri/iris_dri.so: No such file or directory (search paths /usr/lib/xorg/modules/dri, suffix _dri)

[xvnc ] MESA-LOADER: failed to open kms_swrast: Error loading shared library /usr/lib/xorg/modules/dri/kms_swrast_dri.so: No such file or directory (search paths /usr/lib/xorg/modules/dri, suffix _dri)

[xvnc ] MESA-LOADER: failed to open swrast: Error loading shared library /usr/lib/xorg/modules/dri/swrast_dri.so: No such file or directory (search paths /usr/lib/xorg/modules/dri, suffix _dri)

[xvnc ] MESA-LOADER: failed to open iris: Error loading shared library /usr/lib/xorg/modules/dri/iris_dri.so: No such file or directory (search paths /usr/lib/xorg/modules/dri, suffix _dri)

[xvnc ] MESA-LOADER: failed to open kms_swrast: Error loading shared library /usr/lib/xorg/modules/dri/kms_swrast_dri.so: No such file or directory (search paths /usr/lib/xorg/modules/dri, suffix _dri)

[xvnc ] MESA-LOADER: failed to open swrast: Error loading shared library /usr/lib/xorg/modules/dri/swrast_dri.so: No such file or directory (search paths /usr/lib/xorg/modules/dri, suffix _dri)

[xvnc ] Fri Feb 20 09:33:45 2026

[xvnc ] vncext: VNC extension running!

[xvnc ] vncext: Listening for VNC connections on /tmp/vnc.sock (mode 0660)

[xvnc ] vncext: Listening for VNC connections on all interface(s), port 5900

[xvnc ] vncext: Created VNC server for screen 0

[xvnc ] [mi] mieq: warning: overriding existing handler 0 with 0x1510c2e4f0bd for event 2

[xvnc ] [mi] mieq: warning: overriding existing handler 0 with 0x1510c2e4f0bd for event 3

[supervisor ] starting service 'openbox'...

[supervisor ] starting service 'xcompmgr'...

[supervisor ] starting service 'dbus'...

[supervisor ] starting service 'xrdb'...

[supervisor ] starting service 'nginx'...

[nginx ] Listening for HTTP connections on port 5800.

[supervisor ] starting service 'app'...

[supervisor ] all services started.

[supervisor ] service 'xrdb' exited (with status 0).

[app ] Logging to /config/log/qdirstat.log

[xvnc ] Fri Feb 20 09:35:45 2026

[xvnc ] Connections: Accepted: /tmp/vnc.sock

[xvnc ] SConnection: Client needs protocol version 3.8

[xvnc ] SConnection: Client requests security type None(1)

[xvnc ] VNCSConnST: Server default pixel format depth 24 (32bpp) little-endian rgb888

[xvnc ] VNCSConnST: Client pixel format depth 24 (32bpp) little-endian bgr888

I reinstalled the container and have the same issue...thoughts?

How the problem started ?

1 hour ago, Djoss said:

How the problem started ?

Unclear...I opened it up like I usually do and it's just not working for me. Perhaps it's just me then if nobody else is reporting issues. It's been a few months since I last used it.

Does the problem appeared after a container image update ?

Can you share the output of the following commands:

• docker logs QDirStat

• docker inspect QDirStat (remove any password from the output if you configured some)

Docker Inspect QDirStat.txtQDirStat Logs.rtf

Logs attached. I updated the container, no change. I also installed another QDirStat container and have a similar issue (not exactly, but similar). Something is wonky in my display driver perhaps?

The errors you are seeing should not prevent the UI from being displayed. Did you try with another browser, or in an incognito/private window ?

You can also try to disable the privileged mode.

As suddenly as it started, my issue has disappeared. The container is working as expected again.

How i can start a Scan on Boot?

So the Docker Container started and Start a Scan and this must not manually and not waiting for finished than, this can be huge time by large Storage Size.

And how i can change the Language?

Edited May 9May 9 by Revan335

To my knowledge, QDirStat doesn't support an automatic scan on start. Same thing for other languages.

Maybe these are something you can ask on https://github.com/shundhammer/qdirstat

50 minutes ago, Djoss said:

To my knowledge, QDirStat doesn't support an automatic scan on start. Same thing for other languages.

Maybe these are something you can ask on https://github.com/shundhammer/qdirstat

Linuxserver have a Language Option 🤔: https://docs.linuxserver.io/images/docker-qdirstat

I don't test this actually.

This container also has a language option: https://github.com/jlesage/docker-qdirstat#environment-variables

But if the dockerized application (i.e. QDirStat) doesn't have any translations, it won't help.

11 hours ago, Djoss said:

QDirStat doesn't support an automatic scan on start.

Is that helpful? https://github.com/shundhammer/qdirstat/issues/305

Edited May 11May 11 by Revan335

@Djoss Or can not include this in the Template or the Docker Container?