Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


Posts posted by sonic6

  1. 37 minutes ago, ados said:

    I used it all the time on hover of the docker icon, allowing you to see graphs of RAM, CPU etc, over the past interval.


    if you add this, you should add a notice about that: 



    39 minutes ago, ados said:

    Edit: also the ability to upload icons rather than URL 🙏

    you can just download icons, put it into a folder on your server and use it:



    keep it simple

  2. 1 hour ago, domrockt said:

    looks fine and thx for a new Docker thats sorting, but i have dockers not showing in the correct Folder, it is completly wrong and all my dockers are scrambled


    4 hours ago, Takiyon said:

    Apps not showing in the proper folder that is was selected.


    did you try this:


    15 hours ago, scolcipitato said:

    Your unraid order is wrong, to fix it just reorder a container then refresh.


    if this will not help, maybe a debug-log will be helpfull for @scolcipitato

  3. 37 minutes ago, keywal said:

    Might I ask why you are reinventing the wheel though? 

    I'm sure Squid would be delighted to hand over the original. I believe he said as much when he forked it last year some time?


    Because Squid that "the wheel must be reinventing though":


    • Like 2
  4. Ein Kurzes simples Skript um (stark) komprimierte Backups der LXC Container zu erstellen.


    Da @ich777 mit der Version 2023.07.30 eine Backup eingeführt hat, ist mein Skript in der ursprünglichen Form "überflüssig" geworden.

    Nähere Informationen erhält man mit Folgenden Befehlen im Terminal:

    lxc-autobackup -h
    lxc-autosnapshot -h

    Dahingehend habe ich mein Skript angepasst um mehre Container nacheinander zu Sichern:


    Als Anfänger kann man sich grob an meiner Anleitung für das Pi Image Backup langhangeln.


    Folgende Dinge sind vorab zu beachten:

    -Backup Share oder Unterordner (falls gewünscht) im Share erstellen.

    -Bitte nur die Variablen Anpassen:

    • LCX_CONT_NAMES: Alle zu sichernden Container durch Kommata getrennt eintragen
    • BACKUP_PATCH: Pfad zum Backup Share. Der Ordner muss vorher angelegt werden. Unterordner mit dem Namen des Containers werden automatisch erstellt.
    • COM_LVL: Stärker der Kompression.
      0 = niedrig, bis 9 = hoch. !!ACHTUNG!!! 7 bis 9 benötigt bis zu 12GB RAM!!
    • BACKUP_COUNT: Anzahl der zu erhaltenen Backups. Das älteste wird gelöscht.
    • CPU_THREADS: Anzahl der genutzten CPU Threads (nicht Kerne). Wer hier nicht weiß, was er tut, lässt den Wert auf "default" stehen. Bei "default" werden 50% der System-Threads genutzt.
    • USE_SNAPS:
      0 = Es wird eine Sicherung des Containerimage OHNE Snapshots gemacht. Der Container ist während des kompletten Sicherungsvorgang offline/gestoppt.
      1 = Der Container wird zur Erstellung einen Snapshots gestoppt. Danach wird der Container gestartet und der Snapshot wird gesichert. Das KANN den Vorteil haben, dass der Container schneller wieder gestartet wird/online geht.



    Die Verwendung des Kompressions-Levels von 7 - 9 kann in einer hohen RAM Auslastung von bis zu 12GB resultieren!

    Bitte mit Vorsicht nutzen!


    ###LXC Container Backup###
    LXC_CONT_NAMES="CONTAINER1,CONTAINER2,CONTAINER3" #Name der zu sichernden Container getrennt durch ein Komma ohne Leerzeichen
    BACKUP_PATH="/mnt/user/YOUR-BACKUP-SHARE"   #Pfad zum Backup Share
    BACKUP_COUNT="5"    #Anzahl der zu erhaltenen Backups
    COMP_LVL="6"    #Compressions Level (0 - 9 ACHTUNG! 7-9 benötigt bis zu 12GB RAM)
    CPU_THREADS="default"   #Anzahl der zu nutzenden CPU Threads (0 = ALLE / default = haelfte)
    USE_SNAP="1"    #Snapshot verwenden (1 = aktiviert, 0 = deaktiviert)
    #splitt Containernames
    IFS=',' read -ra CONTAINERS <<< "$LXC_CONT_NAMES"
    for container in "${CONTAINERS[@]}"; do
      if [ "$USE_SNAP" -eq 1 ]; then
        if [ "$CPU_THREADS" = "default" ]; then
          lxc-autobackup -s -n="$container" -p="$BACKUP_PATH" -b="$BACKUP_COUNT" -c="$COMP_LVL"
          lxc-autobackup -s -n="$container" -p="$BACKUP_PATH" -b="$BACKUP_COUNT" -c="$COMP_LVL" -t="$CPU_THREADS"
        if [ "$CPU_THREADS" = "default" ]; then
          lxc-autobackup -n="$container" -p="$BACKUP_PATH" -b="$BACKUP_COUNT" -c="$COMP_LVL"
          lxc-autobackup -n="$container" -p="$BACKUP_PATH" -b="$BACKUP_COUNT" -c="$COMP_LVL" -t="$CPU_THREADS"


    Ursprüngliches Skript:


    Der Inhalt des Backups ist der Container selbst, die erstellten Snapshots und die Config.

    Das Skript lastet den Server recht stark aus, dafür ist die Komprimierung sehr platzsparend.

    Hinzu kommt eine recht hohe RAM Auslastung von circa 12GB.


    Als Anfänger kann man sich grob an meiner Anleitung für das Pi Image Backup langhangeln.


    ###LXC Container Backup###
    LXC_CONT_NAME="CONTAINER NAME"				#LXC Container Name aus dem UI
    BACKUP_PATH="/mnt/user/YOUR-BACKUP-SHARE"	#Pfad zum Backup Share
    BACKUP_COUNT="5"							#Anzahl der zu erhaltenen Backups
    CPU_THREADS="all" 							#Anzahl der zu nutzenden CPU Threads (Nummer oder "all")
    #dont change
    DATE="$(date +%Y%m%d)"
    REAL_BACKUP_PATH="$(realpath -s ${BACKUP_PATH})"
    #check LXC setup
    LXC_PATH=$(cat /boot/config/plugins/lxc/lxc.conf | grep "lxc.lxcpath=" | cut -d '=' -f2-)
    #stop + backup
    lxc-stop -n ${LXC_CONT_NAME}
    umount ${LXC_PATH}/${LXC_CONT_NAME}/rootfs 2>/dev/null
    if [ ${CPU_THREADS} != "all" ]; then
      tar -cf - . | xz -9 --threads=${CPU_THREADS} > ${REAL_BACKUP_PATH}/${LXC_CONT_NAME}/${LXC_CONT_NAME}-${DATE}.tar.xz
      tar -cf - . | xz -9 --threads=$(nproc --all) > ${REAL_BACKUP_PATH}/${LXC_CONT_NAME}/${LXC_CONT_NAME}-${DATE}.tar.xz
    #delete old backups
    pushd ${REAL_BACKUP_PATH}/${LXC_CONT_NAME}; ls -tr ${REAL_BACKUP_PATH}/${LXC_CONT_NAME}/${LXC_CONT_NAME}* | head -n -${BACKUP_COUNT} | xargs rm; popd
    lxc-start -n ${LXC_CONT_NAME}




    Backup wiederherstellen:

    Öffne das Terminal und nutze folgenden Befehl um die autoback Funktion aufzulisten.

    lxc-autobackup -h

    Hier werden die Möglichkeiten und Beispiele für die Wiederherstellung angezeigt.



    Danke an @ich777 für das LXC Plugin, Inspiration, Code-Schnipsel und Hilfe!


    Bitte berücksichtig, dass ich selbst sehr wenig Erfahrung habe, daher bin ich für Feedback und Ergänzungen sehr dankbar!

    • Like 2
  5. 2 hours ago, Arbadacarba said:

    How do we reorder the items in Dockers and VM's? I thought you just dragged them but can't seem to get that to work.


    create or edit a folder, scroll a bit down, then hold swipe the container, you want to change the position.


  6. 7 hours ago, scolcipitato said:

    If you want it now, here is the link.

    maybe better changing it to this one: https://raw.githubusercontent.com/scolcipitato/folder.view/main/folder.view.plg


    when i try installing it: 

    plugin: installing: folder.view.plg
    plugin: downloading: folder.view-2023.07.28.txz ... done
    plugin: bad file MD5: /boot/config/plugins/folder.view/folder.view-2023.07.28.txz
    Executing hook script: gui_search_post_hook.sh
    Executing hook script: post_plugin_checks



    It also supports data:image/{type};base64, format (Convert image to data strings)

    what is the benefit of this?

    i just downloaded *.png and put it into a seperate folder in my appdata on my cache drive.

  7. 10 minutes ago, scolcipitato said:

    TLDR; reorder the folder if you need the autostart to work correctly.

    isn't this the same, like it was before and unraid works by default? all containers starting by their position in order from top to bottom?

  8. 10 hours ago, scolcipitato said:

    This is the plan, but as you said I want to rename it to something different, I just don't have any ideas for a new name (I don't think 'Folders' is not a good name).

    I wouldn't recommend putting "Docker" or so in the Name. Maybe you will add LXC support, or something else in the futur. But a Name with "Folders" inside should be necessary.


    How about "App Folders" or "Unraid Folders"?

    ("Apps" because of Community"Apps", what the Folders are most for)

  9. 5 minutes ago, shpitz461 said:

    Have we lost the ability to click on a container icon and get to see cpu/mem usage graphs

    just a side info:

    this cause a higher CPU load / RAM usage to your sever, even when the webgui isn't open. it is the same with the "adavned view"... you don't want to use that, it just wasting a lot power.

  10. 2 minutes ago, shpitz461 said:

    I don't see the containers list below the options, only the toggle entries below:


    I haven't rebooted since installing the new plugin over the old one (didn't uninstall the old one 1st).

    First, backup you settings from the old Plugin. Like do some Screenshots,... then unistall the old one.

    • Thanks 1
  11. 9 minutes ago, scolcipitato said:

    I don't know if it is better to create a new one and have the two plugins on CA at the same time or have only this one.

    i would recommend contacting the Dev Team. there a some deprecate plugins from the past and they know, how to handle that case.

  12. 1 hour ago, shpitz461 said:

    When I'm on the docker tab and unlock movement, I still can't drag any of the containers.


    28 minutes ago, 1471 said:

    Same issue on a fresh, trial install of 6.12.3, PM'd with more @scolcipitato with some more info

    you have to do it here:


    create or edit a folder, scroll a bit down, then hold swipe the container, you want to change the position.


    @scolcipitato maybe you have to add an icon, or something that indicates how and were to move the container position inside a folder?

  • Create New...