Nodiaque

Oh! That is different then. I'll check it later on.

Hello, as stated in the FAQ, in the first page and in the docker description, the docker doesn't contain the game itself thus doesn't have any version. To update, simply restart the docker to restart steam and download the latest version. Sometime, the steamcmd doesn't detect change and you need to delete a file (see second post) to force the update.

Oh didn't knew this existed, thanks

I'm a bit trying to understand that vs backup/restore appdata plugin?

@Squid I was wondering if you have any idea of what's going on. Thank you

Redis itself (at least the official docker) doesn't use environment variable. It use the config file. I strongly suggest switching to config file instead for ongoing support

Summary: Support Thread for Nodiaque Pihole docker Application: Pihole Official DockerHub: https://hub.docker.com/r/pihole/pihole/ Pi-Hole - let's block those pesky ads! This is a template for the official PiHole Docker. Easiest way to setup is using a custom network for eth, select it in network and enter custom IP on your network. You can also use bridge mode. You cannot use host mode since Unraid is already listening on the DNS ports. If you set you router to give out the PiHole address to clients, make sure that you fix the unRaid servers dns to point to a real DNS Server. Please check https://hub.docker.com/r/pihole/pihole for additional variables that you may need. For all pihole specific help, please head to pihole official forum. This app is simply a wrapper of the official docker without any modification.

I'll tell you how I setup my pihole and docker network. I have many container with their own ip. You will need to enable advanced view everywhere. I use macvlan and enable host access. This is not required but I do need it for my own scenario. Then, enable IPv4 custom network on interface eth0. This should be the same range as your router. Then, in you docker, you will select the custom eth0 network. After that, you will see a place to put a fixed address right under it. Be sure that in "extra parameter", you have this: --cap-add=NET_ADMIN --hostname=hostnameofyourpiholehere After, in the template, you should see "serverip" and "serveripv6" (at least my template have). If your template doesn't have it, just create it Under value, it should be the same ip you used for fixed ip. I'm looking at the pihole available in the list and it seems the one I used isn'T listed anymore (but it's using the official pihole docker). I see binhex does also use the official docker so it should work if you add it in that docker. I honestly see way more option in mine but it might be option I added by reading the pihole wiki. You could use bridge mode. I don't like bridge mode cause it's putting the pihole in it's separate vlan, not what I like. I want them directly on my vlan and that's how I learn to do it. Running over multiple vlan is easier with custom docker network then using default bridge. There's also benefit on using custom vlan vs bridge but I won't go into that here. I did create a docker pihole with all the var I use. There's many other you can use and the link for them is in the description. It should appear soon in the CA tabs. It's by default in bridge mode.

I myself run pihole on unraid. It's not bad, you just have to think to have 2 dns. That's why I have another unraid running on a small server that I call HA that is running a duplicate instance of each network critical component like DNS. That's the way to go. You can use Pi or anything you want to run pihole. Everything can go down, even a pihole. We have unraid server that have years of uptime (not OS updated) and I've saw pi rebooted daily. Now for the DNS question, here's how OS work. First, they get the DNS from your DHCP. If you are using pihole, the DHCP should only distribute the IP of the pihole. I'll get on to why later. If you have multiple PiHoles, the DHCP server should give all of them (or at least those you want to be used). The client itself use a round robin way for queries. Your computer does a lot of queries and this is done to be sure a server doesn't get overloaded. The primary server do tend to receive more query. If the server it query fail as unreachable, it will try to contact another DNS in the list. It doesn't keep a tab on who is up or not, so it might try again for another query on the unreachable server. This can cause latency, but won't stop your Internet from working. That's how all of the internet work (without talking about Load Balancer and other stuff like it, simple flat explanation). It is not a list of server 1, then 2, then 3, it's round robin random style. If you are running windows, run ipconfig /all in a cmd and you will see under DNS a simple list, no priority. Now, why don't you want your DHCP to broadcast both the PiHole DNS and the router DNS? Normally, you would configure pihole to use your router DNS. The reason is PiHole won't know anything about local network if you connect it directly to an internet DNS. You can do it, but you need to make other configuration in PiHole to forward those type of dns query to the router. For a beginner, it's just easier to connect to the router DNS. But the reason to not send the Router DNS to the client is because of the round robin said earlier. By doing this, it means that some query goes to pihole, some goes to the router. Which mean that if you block in pihole a website, like www.xxx.com, if at the time of the request, the computer query the router, it won't be blocked. Don't forget that a computer also have a cache DNS. When a domain name is resolved, it cache the information for a certain amount of time (and browser can have their own cache also seperate of the OS, Edge and Chrome are notorius for that). Which mean that if you resolve and address and then block it, it could still work for a while. That's why in the documentation, it is recommended to close all browser and clear local dns cache of the client when testing; sometime even a reboot.

honestly, you could just spin a redis native one. Once Bitnami goes down, so will all your redis container. There's 2 I could find, the one from jj9987 which is a plain redis, no path mapping and config file. Just launch and forget (which mean no option and also not running with unraid docker user) and the one I created (there's a bug in the template, read description to fix, still waiting on return on why it's doing that) that comply with unraid user and permission. With the one I created, you have a persistence path (which is required to backup your data) in which you can plug your current bitnami data. The second path is the one that is bug, it should end with /config/. This is where you will put the redis.conf. The template show you where to get the redis.conf template. After, you need to check if in the current container appdata, you have a folder "appendonlydir". If so, you need to enable appendonly in the config. I suggest you read the config file. The default config file container run without a password in protected mode, which mean nothing can connect to it. You need to edit the file for "requiredpassword" to add a password and/or change the binding so it listen to everything. The template explain very well everything required. I myself did it for immich, nextcloud and authelia. Moved over my 3 instances from bitnami to my container using the same config file (but different password).

Hello, I have a template I did for redis which I did like all my other template (create on my system, click save, copy/paste and remove extra stuff like date installed). In the template, I have 2 path but weirdly, when I installed from the CA, the second path is truncated: XML: CA New installation (ran from another server that never installed it): XML: unraid_template/nodiaque/redis.xml at master · nodiaque/unraid_template Can someone help me understand why? I've checked under invalid template and template error and all I find is Duplicated Template: Nodiaque's Repository - redis - redis But I only have 1 xml for redis so I don't understand. Thank you

You could also simply take a proper redis container and use redis.Conf, and configure in that config file no password. Problem with custom one is when the owner stop updating or remove all its container like bitnami will in September, you will be left with container without update and no recovery if you need to rebuild.

passwordless means protected mode off also. I'm unsure how long this will be supported. On the one I just put online, you create the config file and you have 100% control over it. There's also no persistance on that redis container edit: there seems to be a bug with my template and I don't get why. My template put a /conf/ path but when you add it from the CA, the path is truncated. Currently investigating

Ah, I though it was someone else immich image. Mine is up for the last year if not more and stable so I haven't done anything beside container update. I was using bitnami redis that just broke and just made my own container with the official redis instead (and also created a template). Is there a gain to go with valkey?

What's the difference with the docker from ImageGenius? It's the one I'm running that use immich-postgresql and a redis database (not vaultkey).