-
[Support] devzwf - pihole DoT/DoH
Thank you for the quick fix. Stubby is working fine so far. 👍 Regarding gravity update interval: Were you able to find a solution by any chance? 🙃
-
[Support] devzwf - pihole DoT/DoH
@ZappyZap Thank you for this container. Its working great. 👍 I have 2 questions, though: - I recently deployed a fresh v6 and noticed, that there is no stubby config file in /config anymore (as it was in v5). How does one change stubby config? - I'd like to change the automatic gravity update interval. As changing it via crontab -e won't persist and, if I understood correctly, according to this blog just exposing /var/spool/cron/crontabs/root will create a lot of problems even with correct user/permissions, would you be willing to implement a solution for that?
-
-
[7.0.0-beta.2] docker apps not starting with assigned mac-address after reboot or array restart
Hi, as the title suggest, I noticed a bug that, when starting a docker app after reboot or array restart, they won't use the mac-address predefined in "Extra Parameters". Doesn't matter if using "--mac-address=02:42:xx:xx:xx" or "--mac-address 02:42:xx:xx:xx" This is true for both linuxserver/emby and linuxserver/plex and both are connected directly to the network, with their own predefined IP and under a different VLAN than what the server is in. Weirdly enough a third docker app (jonarin/glftpd), with the same setup (also connected directly and to the same VLAN), is not showing this symptom. Haven't noticed this on any earlier release. I'm assuming it's related to the current beta. Steps to reproduce: - Stop and restart the array and/or reboot the server - start the dockers - they will start up perfectly fine and use the assigned IP but with a different MAC Workaround to fix: - with the array and docker running, modify anything in the template or force-update the docker app Does anyone have an idea how to fix this? diagnostics-20240929-2341.zip
-
[solved] setting up a docker from dockerHub (glftpd) on a fresh unraid (6.12.6) install
I have a different poolname (and path). I had it simplified to make it easier to read. But thanks for pointing it out To avoid confusion I will change it 🙂
-
[solved] setting up a docker from dockerHub (glftpd) on a fresh unraid (6.12.6) install
I was able to solve it by changing the file as follows: version: '3.9' services: glftpd: image: jonarin/glftpd container_name: FTPd restart: unless-stopped networks: default: ipv4_address: 10.10.099.243 ports: - 23830-23840 environment: - GL_RESET_ARGS=-e - TZ=Europe/Zurich - GL_PORT=23840 volumes: - '/mnt/myshare/ftp/conf:/glftpd/ftp-data' - '/mnt/myshare/ftp/data:/glftpd/site' networks: default: external: true name: bond0 It's not pretty but it seems to work. If anyone has a better solution please let me know 🙂
-
-
[solved] setting up a docker from dockerHub (glftpd) on a fresh unraid (6.12.6) install
@mods: I hope I'm in the right subforum. Seemed to be the most fitting. If not, please send me a pm TL;DR: fresh unraid install (version 6.12.6). trying to get https://github.com/jonathanbower/docker-glftpd to work and failing hard. Unable to get a direct network connection (prefered) and/or mapping on host. Hi guys, I recently (re-)installed a fresh unraid with version 6.12.6 and set up everything up from scratch. No specific in-depth config/tweaks. Everything's rather default. All my previous dockers are working fine except glftpd (the docker I'm using: https://github.com/jonathanbower/docker-glftpd) although using the exact same template as on the previous install. The issue: it doesn't matter if or what network I specify, it won't establish a network connection (I prefer glftpd having its own IP) or map the ports on the host. No errors shown in docker-log. My current network settings: dual-nic bond (active-backup) bridging disabled macvlan enabled My compose file (using the Compose.Manager-Plugin) I used before and was working like a charm version: '3.9' services: glftpd: image: jonarin/glftpd container_name: FTPd restart: unless-stopped networks: bond0: ipv4_address: 10.10.099.243 ports: - 23830-23840 environment: - GL_RESET_ARGS=-e - TZ=Europe/Zurich - GL_PORT=23840 volumes: - '/mnt/myshare/ftp/conf:/glftpd/ftp-data' - '/mnt/myshare/ftp/data:/glftpd/site' networks: bond0: external: true name: bond0 What I tried so far: all combination of bond on/off, bridging on/off, ipvlan/macvlan. but no dice. Previous (working) setup on old install: bond on + bridging on + macvlan (I know, not recommended anymore, but it was a legacy setup and had no issues whatsoever) specifying all available docker networks/-types Since I'm no docker expert in any regard, does anyone have any idea on how to get it (back) working (again) or any hints where to look? Thanks in advance paddesb
-
Apps loading error
not exactly sure if this is the correct subforum but same issue here. started ~1h ago @Squid is it an issue with community application or something else?
paddesb
Members
-
Joined