Jaburges

Members
  • Content Count

    78
  • Joined

  • Last visited

Community Reputation

1 Neutral

About Jaburges

  • Rank
    Newbie

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Ah it seems the magic is with a CNAME not an A record. I used to use a shell script that allowed for A records, but this CNAME set up with docker seems easier
  2. are people still able to use this?? It seems Godaddy is now forcing the use of an IP address x.x.x.x in the 'points to' for the A record 😞
  3. Hey folks, Not really sure what happened - all of a sudden getting errors: Get Docker Details for ip: 192.168.x.x Failed Request failed with status code 503 Get Main Details for ip: 192.168.x.x Failed Request failed with status code 503 Get VM Details for ip: 192.168.x.x Failed Request failed with status code 503 Get Docker Details for ip: 192.168.x.x Failed Request failed with status code 503 Get Dashboard Details for ip: 192.168.x.x Failed with status code: [object Object] Tried adding privileged to the docker. Didn't work Tested I can access the docker.sock remotely ok
  4. weird - no clue why its looking in sys/ what is the full error - what file is pointing to that?
  5. you downloaded 5.10.1 as above? Have you tried the make command? does it fail on missing files? if so goto /usr/src/linux then run `find -name XXXXX` where XXXX is the file that is missing from the make.
  6. Ok so got it working on 6.9.0-rc2 (Huge thanks to @pgbtech for the initial steps helping me solve some issues I had) Rough workflow is: 1. Download Coral gasket and apex sourcefiles 2. Download and extract Linux kernel 5.10.1 (6.9.0-rc2), and copy over Unraid patches/mods 3. Install dependencies and add symlinks 4. make gasket and apex 5. add to drivers and boot config 6. Enjoy I also enabled all of the DevTools plugin as well (make for example is needed) [Please note at time of writing, the symlinks didnt bring all the required fil
  7. little out of my depth but the top of the file in question: `errno.h` #include <uapi/linux/errno.h> there are a bunch of *.h (limits.h, errno.h) that look for `uapi/linux/file.h` Not sure if i'm doing something wrong, but the files are all over the place and thus not found by the make command. So either need editing, moving, or another symlink created I created another symlink ln -s /usr/src/linux/include/uapi /usr/include/uapi But i still get errors with other files not located where they are expected. @DiabloXP did you copy
  8. Thanks for sharing It seems the makefile is looking for a file uapi/linux/error.h /usr/src/linux/arch/x86/include/uapi only contains `asm` directory are there any other symlinks that you added that may resolve this?
  9. i must be doing something wrong. Running Unraid 6.9.0-rc2 Bison 3.0.4 (as per guide above) Linux kernel (according to 6.9.0-rc2) is 5.10.1 getting an error on make modules_prepare SYNC include/config/auto.conf.cmd HOSTCC scripts/basic/fixdep HOSTCC scripts/kconfig/conf.o In file included from /usr/include/bits/local_lim.h:38, from /usr/include/bits/posix1_lim.h:161, from /usr/include/limits.h:183, from /usr/lib64/gcc/x86_64-slackware-linux/9.2.0/include-fixed/limits.h:194,
  10. Did you use the exact steps or edit for Unraid kernel 5.1.0 as you are on 6.9.x ?
  11. OMFG - no I didn’t - this is gold! Thanks for sharing! I’ll give this a try for 6.9.x
  12. Moved from the wrong area: Hi Folks, So this wasn't as easy as I thought as the host OS needs the drivers. According to the instructions: Get started with the M.2 or Mini PCIe Accelerator | Coral I need to install these packages: sudo apt-get install gasket-dkms libedgetpu1-std However apt-get isn't available on Unraid - bugger The odd thing is the device shows up in lspci - so i'm wondering if I can still use it? I'm not sure if I can find the device on the host and map it to the docker. Is there a way to run the drivers in ano
  13. @dlandonJust pointed a friend to the Unraid template and its missing the ENV variables for hook processing and Yolo etc. Is it still actually there and they can add it manually or will they need an older dockerfile?
  14. I guess there a few options: 1. community maintain the zoneminder docker 2. Consider separating the ML components to a separate docker and Zoneminder docker 3. move to another NVR docker like Shinobi, motioneye, blue iris (Shinobi has tensorflow built in, but there is deepstack or frigate for object detection docker components). happy to help where I can
  15. Sorry it’s been a burden, it is a huge complicated docker, and you’ve put a lot of great work into creating this. We and Zoneminder owe you a lot of thanks! in terms of the best way to approach Zoneminder moving forward - could a micro services approach work? It will add a little more overhead but would it make sense to have Zoneminder + SQL + Eventserver (hooks) and then could be docker composed together or upgraded individually? thinking a no-hooks ES, and a hooks ES? I could be over simplifying? my knowledge isn’t super deep, but If I can help LMK