Posts by theking2

  • global environment

    I'm trying to understand this.

    • There is the Configs tab in services compose
    • There is an environment file section in each compose file

    Are these two related?


    (in my defense the word "configs" does not appear in https://wiki.omv-extras.org/do…v7_plugins:docker_compose


    Thread
    Example for the configs tab in compose?
    Hi, Does anyone have an example compose file that uses the config tab? I think I understand what the intent is, but I'm not clear how to implement. I have one container where it might be relevant to me, eclipse-mosquitto. This container needs a mosquitto.conf file with details about my network and queue parameters. It gets bind-mounted into the container, but that and a logging directory are about all it needs from the host.
    1) Is the intent of the configs tab for use cases like this? So I can…
    jimko

  • Notification emails formatting

    I like the update notifications. but they contain way more information than needed. Is it possible to make them more useable?


  • CHANGE_TO_COMPOSE_DATA_PATH and PATH_TO_DATA and ${{ "..." }}

    yes, it changes fine. this is the log after:


    Quote

    docker compose logs ...

    invalid interpolation format for services.lms.volumes.[]. You may need to escape any $ with another $. ${{ sf="media" }}/audio/music:/music:ro

    *** ERROR #1 ***

    END OF LINE

    This is the new fiel


    It seems to do this in journalctl:

  • global environment

    One use case would be my "media" share. I use media/music for my Lyrion Media Server and media/video for my minidlna server. It works also with using the aboslute path bot for consistancy `${{ sf="media" }}` would make sense.

  • CHANGE_TO_COMPOSE_DATA_PATH and PATH_TO_DATA and ${{ "..." }}

    Quote from chente

    I suggest you read the Docker documentation for OMV8. The new automatic replacement feature of the Compose plugin in OMV8 has relegated global variables to the background.

    https://wiki.omv-extras.org/do…tutions_in_a_compose_file


    This new workflow is much more intuitive, maintainable, and easy to understand.

    docker compose logs ...

    Code
    invalid interpolation format for services.lms.volumes.[].
You may need to escape any $ with another $.
${{ sf:"media" }}/audio/music:/music:ro

  • upgrade went flawless

    A word of great appreciation to the developers of OMV. Todays upgrade on my Pi5 based four SSD NAS went flawless. After all downloading, compiling and installing the reboot was smooth and with zero problems. All 10+ containers booted quick and without an itch. on Version 7.7.24-7 (Sandworm) now.


    Great work 💯

  • Consistant errors when mounting

    perhaps a bit more info:


    • wiped the usb disk
    • created a F2FS file system
    • Mount the partition
    Quote

    Create file system

    Creating new GPT entries in memory. Disk /dev/sda: 7827456 sectors, 3.7 GiB Model: USB DISK 2.0 Sector size (logical/physical): 512/512 bytes Disk identifier (GUID): AB68C825-8B7D-4BD4-AC76-C7E02ACE2405 Partition table holds up to 128 entries Main partition table begins at sector 2 and ends at sector 33 First usable sector is 34, last usable sector is 7827422 Partitions will be aligned on 2048-sector boundaries Total free space is 2014 sectors (1007.0 KiB)

    Number Start (sector) End (sector) Size Code Name 1 2048 7827422 3.7 GiB 8300 The operation has completed successfully. F2FS-tools: mkfs.f2fs Ver: 1.15.0 (2022-05-13)

    Info: Disable heap-based policy Info: Debug level = 0 Info: Trim is enabled Info: [/dev/sda1] Disk Model: USB DISK 2.0 Info: Segments per section = 1 Info: Sections per zone = 1 Info: sector size = 512 Info: total sectors = 7825375 (3820 MB) Info: zone aligned segment0 blkaddr: 512 Info: format version with "Linux version 6.12.47+rpt-rpi-2712 (serge@raspberrypi.com) (aarch64-linux-gnu-gcc-12 (Debian 12.2.0-14+deb12u1) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT Debian 1:6.12.47-1+rpt1~bookworm (2025-09-16)" Info: [/dev/sda1] Discarding device Info: This device doesn't support BLKSECDISCARD Info: This device doesn't support BLKDISCARD Info: Overprovision ratio = 3.260% Info: Overprovision segments = 128 (GC reserved = 69) Info: format successful

    END OF LINE

  • Consistant errors when mounting

    I consistantly, even after a reboot get these errors when I attempt to mount a usb drive (sda) with a F2FS file system created with OMV

  • Add from Example : cloudcmd

    After an attempt to add a compose setting from example I get this error:

    Quote

    docker compose up -d ...

    Image coderaiser/cloudcmd Pulling Image coderaiser/cloudcmd Error Head "https://registry-1.docker.io/v2/coderaiser/cloudcmd/manifests/latest": net/http: TLS handshake timeout Error response from daemon: Head "https://registry-1.docker.io/v2/coderaiser/cloudcmd/manifests/latest": net/http: TLS handshake timeout

    *** ERROR #1 ***

    I apparently needs authentication (?) Is this something that should/can reported somewhere?

  • Allow hosts for chronyd

    Ok it seems when the sudo session timesout the chronyc script keeps running but no longer has acces. hence the 501. After restarting sudo chronyc it works as promised.