klippertyk

for others... https://docs.unraid.net/unraid-os/manual/docker-management/#re-create-the-docker-image-file https://docs.unraid.net/unraid-os/manual/docker-management/#re-installing-docker-applications I am new to this, so any advice apprciated - pre-req checks or gotchas would be useful.

I'm having the same issue - my docker.img is 42.9gb. I've had this error for a while actually and only got around to invesitgating the problem recently. Can I please ask - are there updated links for your articles above? They appear to be out of date. My primary concern is losing my config, my containers took hours to setup - i'm curious as to what is writing to the docker.img though - any tips to investigate that?

I don't think this is an Unraid issue, but as I'm using it on this board, I thought it worth posting. I updated the BIOS to 2802 today from 2305 as part of some prep to update from 6.11.5. When I do a shutdown via unraid, on the next power on, all the drives are no longer detected in POST. I have to powerdown again via IPMI then everything behaves itself. Warm restarts are ok. I'm posting just incase anyone uses this board and has the same issue and if anyone has any ideas why this might be happening (ACPI settings?) as the update blew away my BIOS config so I may have forgotten to set something correctly. This is repeatable. Normal.... Not normal...

just signed up to mullvad but the link in 1st post (and their site) I get a 404. Sooo.... I'm a bit stuck? okaaay had to embarass myself in public to work it out. you have to click account on the top right...

still beavering away at this and my previous comment jumped the gun a bit and didn't solve all my issues. I'm having real trouble getting containers to communicate with each other depending if they are setup to use gluetun or not. I thought I found the answer here which sounds ideal, but I'm on a lengthy NordVPN subscription. At this point I'm prepared to sign up with another provider just to get the VPN tunnel setup but not sure who to go with (I'm based in the UK)

in an effort to fix the prowlarr issue myself, I watched this vid and thought it was excellent. i realised I needed to specify the bridge ip and volia! sorted. Im really interested in try macvlan now though, he's right, the networking in dockers is so cool

Hello! TL:DR - 1. Prowlarr on Gluetun won't connect to other containers not using gluetun's container connection. 2. how to get vpn working for containers generally. I've been scratching my head a little. I've setup the gluetunvpn container to securely provide vpn tunnels to containers. I reviewed spaceinvaders guide to sharing that connection with other containers, and all appeared to be working quite well, I linked jackett via gluetun to sonarr (bridge) and things were going well and the idea was proven. Until I decided to switch from jackett to prowlarr, I need to run prowlarr using gluetun's connection as I did with jackett but when I do, I cannot get it to communicate to sonarr or anything else, switching sonarr over to use gluntun's connection works fine, until I change it back to the container bridge again. Basically I cannot connect to any other containers with prowlarr when it's on gluetun and they are not. browsing several forums, I get the impression this is an "issue" with prowlarr, but I don't understand enough to fix it. Anyone been able to get prowlarr to connect with sonarr or qbittorrent without them also being on a gluetun connection? Which leads me into point 2. My router isn't powerful enough to have an openvpn connection setup on it, else I would do that for all connections and not use gluetun at all, so my question here is, how are you guys securing your containers over vpn (if different to the above) I plan to look at nginxproxymanager next to see what that offers.

Thank you binhex. appreciate your time.

never mind. only needed to change the host port and not the container port. Hello @binhex chimp with a keyboard again and you guessed it, new docker, same(ish) problem. i cant use 8080 and thought after our last adventure I was modifying ports like a boss, alas, on this container, despite me changing ports the log says listening on 8080 and i cant hit the webgui... any faq on this topic?

I understand. As I say I'm quite new to unraid and dockers (but having a blast learning it for my new server) so I was sticking to "what works" as I built my understanding - I didn't have a picture of host vs bridge vs custom bridge, which I learned when puzzling out this issue. I was illustrating that I had vanilla qbit webui working on host, but not in bridge and qbitvpn forced bridge and no webui. Difficult to troubleshoot. What's the reason you mention? FYI - I had to root cause this and test your theory and you were correct, I disabled adblock and it popped up. Thanks for your help and thanks for the time and effort you put into this tooling, really very much appreciated and absolutely adds value to unraid imo.

I would say that is a good theory Binhex yes. I have adblock and ublock origin installed as extensions, but I would have never had guessed that (partly because I had NO IDEA that field was supposed to be there!). A little odd adblock or ublock would take issue with a field to me, but then again, i'm not a code writer either. I was so utterly frustrated by this, I had the log open, I got the vpn working no problems at all, then, to be stumped by the webui... It's worth noting I was checking my logic by removing this docker and installing the vanilla qbit, as it happens I couldn't hit the web ui on any network setting other than host (resolved: my mistake). Which, btw... if I try and setup qbitvpn with host as the network setting, it falls over and doesn't create the docker at all... in case you're interested..

6.11.5 on chrome. It's basically a new deployment. I'll try edge... oh my days, there it is.... you know, for someone new, this was really really puzzling. I'll consider myself rather unlucky eh? I'll give it a try.

wait... If I select the drop down as "path" i see name container path host path default value access mode description but when i select port - I get what I stated

OMG! No! No there is not! I now have a setting called Custom Host Port 1111 and in orange underneath it says Container Port: <blank>