CasaP

Members
  • Posts

    11
  • Joined

  • Last visited

CasaP's Achievements

Noob

Noob (1/14)

2

Reputation

  1. Anyone still having MacOS issues, I would suggest the separate smb-fruit.conf file approach as shown here; After I did this, everything just worked and it is fast as hell...
  2. Anyone still having MacOS issues, I would suggest the separate smb-fruit.conf file approach as shown here; After I did this, everything just worked and it is fast as hell...
  3. One thing to watch out for, I had two config folders, one located at etc/openvpn & another at config/openvpn. In the docker setup /config is mapped to the host folder. It seemed to be getting confused by the second folder. I just mapped the additional etc/openvpn to the host folder also and it fired up just fine.
  4. Does anybody know a resolution for the "infinite loop" issue? I have a simple stack to change Youtube videos from VP09 / Opus to hvec/AAC so safari on Mac can use them. I can use mandrake to do this just fine, but when I use ffmpeg with havoc_nvenc I just get this annoying error, with no real solution. I am using the three plugins in the stack; Tdarr_Plugin_00td_filter_by_size Tdarr_Plugin_075a_Transcode_Customisable Tdarr_Plugin_a9he_New_file_size_check Pulling my hair out. This is wasting a tonne of time, as it transcodes the video just fine, then spits this error at the end.
  5. After updating to 6.11 I began to have issues with yt-dlp based containers (YouTube-DL & TubeArchivist). In case any one else started to get the [errno -2] issue after updating, I found after a lot of hair pulling and tweaking that Docker was not resolving the DNS properly to the containers (in Bridge Mode), and they were thus unable to resolve URL's. Manually editing the /etc/docker/daemon.json file to include the following line of code allows the containers to again resolve URL's. "dns": ["8.8.8.8","8.8.4.4","1.1.1.1"] The contents of my daemon.json looks like this for context; { "runtimes": {"nvidia": {"path": "/usr/bin/nvidia-container-runtime","runtimeArgs": []}}, "dns": ["8.8.8.8","8.8.4.4","1.1.1.1"] } I also managed to automate the code insertion due to the lack of persistence of config files in the OS, by adding the following line to my go file in the /config folder on the USB. This line should be at the start gf the go file so it is executed BEFORE docker launches. # Fix the docker DNS issue sed -i '0,/{/a\ "dns": ["8.8.8.8","8.8.4.4","1.1.1.1"],' /etc/docker/daemon.json My entire go file looks like this for context; #!/bin/bash # Fix the docker DNS issue sed -i '0,/{/a\ "dns": ["8.8.8.8","8.8.4.4","1.1.1.1"],' /etc/docker/daemon.json # Start the Management Utility /usr/local/sbin/emhttp & # Chip drivers modprobe jc42 modprobe k10temp modprobe w83627ehf modprobe fam15h_power # Enlarge the LOG partition (because Dynamix System Stats needs at least 186Mb, default LOG is 128Mb) mount -o remount,size=384m /var/log # Binhex (Container update) # curl -o '/usr/bin/runc' -L 'https://github.com/binhex/arch-packages/raw/master/static/x86-64/runc' && chmod +x '/usr/bin/runc' Hope that helps somebody.
  6. I had a lot of Plex related weirdness, basically I built an Unraid server from scratch to replace my old faithful qNAP 853a. The simplest fix was to give the Unraid Plex install a unique name, the error I had was due to a name conflict, try renaming "friendly name" of your Plex server to something unique, mine is "Socks-Plex". Once I did this all issues disappeared.
  7. I had a similar issue, caused by me trying in vain to get OpenVPN running on my server, purging all VPN stuff got me back. I ended up buying a GL-inet Mango and running Open VPN client on it. Do you have VPN installed, i.e. is the server trying to route through TUN0, but it's not setup correctly or corrupt?
  8. Yep, that worked. I left it for about an hour with the log open an all sorts of stuff was downloading / unstuffing and happening!! All up and running now. Just be patient, it seems to be hung on; [mod-init] Attempting to run Docker Modification Logic [mod-init] Applying linuxserver/calibre-web:calibre files to container But if you just leave it alone t sorts itself out.
  9. So I was having issues trying to get this working, (nuked & re-installed 4 / 5 times)then checked the logs... [mod-init] Curl/JQ was not found on this system for Docker mods installing This error is triggered by lack of network on container start-up... So I set Autostart and wait to 5 seconds, now it's pulling some archives and applying it to the image? Will update if working. Seems to be stuck thinking about something.