Posts by Zafkiel

  • Problems with setting up Adguard Home via Docker Compose

    What a coincidence, I just happened to test adguard home on April 28. Before setting it up, I checked out its docker hub and github pages and looked through this forum for any tips or warnings. I followed Soma’s method, like he mentioned in post #7, and it worked fine with the compose plugin.


    My compose file looks like this:

  • Difference between down and stop command? How to properly edit compose file?

    Quote from TOMillr

    So in my example of Plex running in a container, the data written to /config would be "reused" after an down-up-circle as long as I don't change the volume paths in the compose file?

    Yeah, just like the /srv/dev-disk-by-uuid-7f281e78-cec0-4bf2-a4b9-6d9003ebcb4e/Video:/data in your compose file, running "down" will not delete it.


    Quote from theking2

    EDIT: I do not know what CHANGE_TO_COMPOSE_DATA_PATH are.

    You'll find it mentioned in the compose plugin settings and the Docker documentation for OMV.

    omv7:docker_in_omv [omv-extras.org]


  • China DNS

    Quote from njaimo

    on a separate matter, the OMV server requests NTP every 2-3 minutes... I have OMV set up to reach to pool.ntp.org, and I can read the logs in my pfSense that show the frequency. While I suppose it is not a big issue, it seems unnecessary net traffic, every day would be more than fine -- any way to tune the need to reach for NTP in the OMV install ?

    Well, I tried modifying the code, and it should work in theory, but I wouldn't recommend making the change.


    OMV uses chrony as the NTP client. You can open the /etc/chrony/chrony.conf file with a text editor, and you might see:

    Code
    # This file is auto-generated by openmediavault (https://www.openmediavault.org)
# WARNING: Do not edit this file, your changes will get lost.

server pool.ntp.org iburst

    Here is the documentation for chrony: https://chrony-project.org/documentation.html

    Use chronyc -v to check the version of chrony, then refer to the corresponding version of chrony.conf(5) - chronyd configuration file.

    I think what you need are the minpoll and/or maxpoll options.


    Next, please take a close look at this: https://docs.openmediavault.or…html#custom-configuration

    Based on my testing, modifying chrony's environmental variables will cause errors. The only way to add the chrony directives option is through adding custom states (although this may not exactly be considered "adding custom states").


    Please open /srv/salt/omv/deploy/chrony/files/etc-chrony-chrony_conf.j2 with a text editor, search for "iburst", then add the option you need after it and save the file.

    Like this:


    Run omv-salt deploy run chrony to apply the changes.


    Then check /etc/chrony/chrony.conf. In my case, it became:

    Code
    # This file is auto-generated by openmediavault (https://www.openmediavault.org)
# WARNING: Do not edit this file, your changes will get lost.

server pool.ntp.org iburst minpoll 10 maxpoll 15

    In the end, I still have to remind you that this is not a recommended modification. This approach might be no different from directly editing /etc/chrony/chrony.conf. Whether it will be reverted during the next OMV version update is also unknown. Maybe you should ask developers votdev and ryecoaaron for their opinions.

  • China DNS

    Take a look at how reverse DNS works.

    https://www.cloudflare.com/learning/dns/glossary/reverse-dns/

    Quote

    Reverse DNS lookups query DNS servers for a PTR (pointer) record; if the server does not have a PTR record, it cannot resolve a reverse lookup. PTR records store IP addresses with their segments reversed, and they append ".in-addr.arpa" to that. For example if a domain has an IP address of 192.0.2.1, the PTR record will store the domain's information under 1.2.0.192.in-addr.arpa.

    In your example, it's 111.2.168.192.in-addr.arpa., so the actual address is 192.168.2.111.

  • Heimdall has issues with permissions - help?!

    Quote from erbsenzaehler

    Yes. It's in appdata as seen in the tree command. I used the same way of creating that as it's described in omv-extras example on how to configure jellyfin. There it's also put in the appdata folder. Both my calibre-web and the config from jellyfin are setup the same way and they work without a problem.


    I don't get it...

    It's a bit strange. Normally, it should work if it's placed in appdata as well.


    Try this:

    Code
    volumes:
  - ${PATH_TO_APPDATA}/heimdall/config:/config

    Like your jellyfin compose file:

    Code
    volumes:
  - ${PATH_TO_APPDATA}/jellyfin/library:/config

    Since the heimdall folder is created by the Compose plugin with the default permission of root:root, it should work normally if the container automatically creates a folder with specified permissions inside it.


    Code
    volumes:
  - ${PATH_TO_APPDATA}/calibre-web:/config

    However, I don't quite understand why your calibre-web is working fine, lol.

    In the example on Docker Hub, It should be written like this:

    Code
    volumes:
  - ${PATH_TO_APPDATA}/calibre-web/data:/config

  • [Resolved] Jellyfin - Transcoding Driver Mystery

    I noticed that you are using the linuxserver image and the OpenCL-Intel mod.

    Code
    - DOCKER_MODS=linuxserver/mods:jellyfin-opencl-intel

    And there are these errors:

    I took a look at the commits on https://github.com/linuxserver…ree/jellyfin-opencl-intel. In the 6deb5b9 commit from 2 days ago, the address for LEGACY1 was changed from 24.35.30872.22 to 24.35.30872.32, but opening 24.35.30872.32 results in a 404 error.


    In the merged changes before this, it was mentioned that legacy1 provides support for iGPUs before the 12th generation, but since you have an i3-N305, it shouldn't be affected. Everything has returned to square one. https://github.com/linuxserver/docker-mods/pull/996


    Currently, aside from changing VA-API to QSV in the Jellyfin Transcoding settings or testing with the nightly tag, I don't have any other ideas.


    You can wait for a response from others.

  • Permission

    Quote from fantozzi

    /usr/bin/bash is the shell specified. Yes the user has got a password. I log in the shell as "appuser" with password. When I go to the appdata folder and then to the "homepage" folder as example I got the message...


    -bash: cd: homepage: Keine Berechtigung (no permission)

    Maybe you need to check here.