cybrnook

@ich777 @Getn67 Did this develop into anything? I also have a FusionIO 6.4TB drive I could help test with if needed.

In the past I used intel quick sync, and in addition I had to have this in my "go" file: # Setup Intel HW pass-through for Plex transcoding modprobe i915 chmod -R 777 /dev/dri

Confirmed this is fixed in 6.9.0 RC1

Changed Status to Solved

Fixed in 6.9.0 RC1

To all, Has anyone been successful in setting up Cloudflare "Authenticated Origin Pulls" with this container, is it possible? https://support.cloudflare.com/hc/en-us/articles/204899617-Authenticated-Origin-Pulls

Thanks @binhex for the release of v3

Welcome to the club 🙂

Also seeing this same behavior, VM's section of the Dashboard collapses in on itself when I start a VM (even just 1). When I stop the VM, the section in the dashboard appears again. No VM's running Only Debian VM running (formatting seems to have stacked on itself in the docker section): If I collapse the VM section, then the Docker section formatting is again correct:

Pay no mind to my notifications, it's something custom I do on my own, but was easy to generate notificaitons. @Squid If I relocate to top right, it works fine (And has that little gap between): If I put it back to bottom right (where I like it), it doesn't work, which is also the same behavior for bottom left:

Those are still needed. (I added some more screenshots above)

Just wanted to share a quick success story. Previously (and for the past few releases now) I was using @ich777's Kernel Docker container to compile with latest Nvidia. Excited now to see this be brought in natively, it worked out of the box for me. I use the regular Plex docker container for HW transcoding (adding --runtime=nvidia in the extra parameters and setting properly the two container variables NVIDIA_VISIBLE_DEVICES and NVIDIA_DRIVER_CAPABILITIES). To prepare for this upgrade, while still on beta 30: - disabled docker service - upgraded to beta 35 - uninstalled Kernel Helper Plugin - uninstalled Kernel Helper Docker - rebooted - Installed Nvidia Drivers from CA - rebooted - reenabled docker So far all is working fine on my Quadro P2200 Install Nvidia Drivers Docker Settings: Validate in Settings (P2200 and drivers detected fine) HW transcoding working fine

+1

@Squid I hope all is well with you! Just wanted to drop by and point out something I recently noticed, but seems to have been there for a while. I have the Bitwarden_RS docker installed, and it works fine. Starting/Stopping from the GUI works without issue as well. But, what I am seeing is that however the CA Backup/Restore V2 plugin is handling the shutting down of dockers, it seems to not like the Bitwarden_RS docker. When I watch the backup status, I can see when it get's to Bitwarden it just perpetually waits for shutdown, but seems like it doesn't issue the shutdown command, so maybe it has some issue trying to detect the container or the containers status? So, it will just wait for the "Time to wait when stopping app before killing" value to timeout, then kill the docker. If I run a manual backup (did today), and it's sitting in this waiting period, I can then do to the Docker tab in the gui and click and shutdown Bitwarden fine. Once my shutdown from GUI is complete, I check back on the Backup status and it recognizes that the container was shut down and proceeds with the rest of the Docker shutdowns and then does it's thing. Just wanted to bring that up, not sure if there is anything to worry about if it's force killing Bitwarden every time it shuts it down to back it up, I can assume it doesn't like that... EDIT: Looking at it more, it seems to be just how docker stop is handling the container, not specific to this plugin. "docker stop" just doesn't seem to know once the container has shut down.

@ich777 Were there any updates to the template in the latest version, or just in the core itself? I only updated vs uninstall/reinstall. I am getting to have so many values in the template defined I really try and avoid deleting altogether if I don't have to 😁.

Painless update from beta 25

Beta 29, so far so good.

For anyone interested in using the MaxMinds GeoIP2 functionality, here is a phenomenal blog post that covers how to do it! Thanks @GilbN https://technicalramblings.com/blog/blocking-countries-with-geolite2-using-the-letsencrypt-docker-container/#disqus_thread

Don't forget you need to map that same directory where your bitwarden log file is into your swag container. Then also make sure the path in the bitwarden_rs.conf file for fail2ban has the same "container" path. This is mine for example: Bitwarden (I manually created the dir and made it nobody:users 777 since bitwarden seems to be running/setting root for all 🙂 ) Swag: Swag fail2ban / filter.d / bitwarden_rs.conf file: # https://github.com/dani-garcia/bitwarden_rs/wiki/Fail2Ban-Setup # - Set up logging to file > https://github.com/dani-garcia/bitwarden_rs/wiki/Logging # - Set logging level to warn or error # Logged in /bitwarden-log/bitwarden.log [Definition] failregex = Username or password is incorrect\. Try again\. IP: <HOST>\. Username: .*\.$ ignoreregex = Swag / fail2ban / jail.local file entry: [bitwarden_rs] enabled = true port = http,https filter = bitwarden_rs logpath = /bitwarden-log/bitwarden.log bantime = 3600 findtime = 3600 maxretry = 3

Just letting you know you're not alone 🙂, I have been seeing the same. Typically for me just a "Check for updates" reestablishes the connection. I haven't looked any further into it other than that.

@ich777 I found a url from Nvidia that always displays the latest Linux x86 driver. Maybe it can come in handy for something? http://download.nvidia.com/XFree86/Linux-x86_64/latest.txt

@ich777 Once again that Kernel Docker worked awesome 🙂 My notes: # Needed to enable i2cdetect modprobe i2c-dev # Detect current smbus(s) i2cdetect -l | grep smbus # Detect against all until you find 50-57 range, that is your bus (0,1,2,3, etc....) i2cdetect -y 0 0x50 0x57 # Enable the device (per module), path matches bus number echo ee1004 0x50 > /sys/bus/i2c/devices/i2c-0/new_device echo ee1004 0x51 > /sys/bus/i2c/devices/i2c-0/new_device echo ee1004 0x52 > /sys/bus/i2c/devices/i2c-0/new_device echo ee1004 0x53 > /sys/bus/i2c/devices/i2c-0/new_device echo ee1004 0x54 > /sys/bus/i2c/devices/i2c-0/new_device echo ee1004 0x55 > /sys/bus/i2c/devices/i2c-0/new_device echo ee1004 0x56 > /sys/bus/i2c/devices/i2c-0/new_device echo ee1004 0x57 > /sys/bus/i2c/devices/i2c-0/new_device # Display info decode-dimms # Display info side-by-side decode-dimms --side-by-side # Display DIE version (replacing 0-0050 with the i2c bus number followed by a dash then the memory bank number) od -Ax -t x1 -v /sys/bus/i2c/drivers/ee1004/0-0050/eeprom root@noah:~# decode-dimms --side-by-side # decode-dimms version i2c-tools 4.1 Memory Serial Presence Detect Decoder By Philip Edelbrock, Christian Zuckschwerdt, Burkart Lingner, Jean Delvare, Trent Piepho, Hans Geiblinger and others Decoding EEPROM 0-0050 0-0051 0-0052 0-0053 0-0054 0-0055 0-0056 0-0057 Guessing DIMM is in bank 1 bank 2 bank 3 bank 4 bank 5 bank 6 bank 7 bank 8 ---=== SPD EEPROM Information ===--- EEPROM CRC of bytes 0-125 OK (0x74DA) # of bytes written to SDRAM EEPROM 384 Total number of bytes in EEPROM 512 Fundamental Memory type DDR4 SDRAM SPD Revision 1.1 Module Type UDIMM EEPROM CRC of bytes 128-253 OK (0x05F1) ---=== Memory Characteristics ===--- Maximum module speed 2400 MHz (PC4-19200) Size 16384 MB Banks x Rows x Columns x Bits 16 x 16 x 10 x 64 SDRAM Device Width 8 bits Ranks 2 Rank Mix Symmetrical Bus Width Extension 8 bits AA-RCD-RP-RAS (cycles) 17-17-17-39 Supported CAS Latencies 18T, 17T, 16T, 15T, 14T, 13T, 12T, 11T, 10T ---=== Timings at Standard Speeds ===--- AA-RCD-RP-RAS (cycles) as DDR4-2400 17-17-17-39 AA-RCD-RP-RAS (cycles) as DDR4-2133 15-15-15-35 AA-RCD-RP-RAS (cycles) as DDR4-1866 13-13-13-30 AA-RCD-RP-RAS (cycles) as DDR4-1600 11-11-11-26 ---=== Timing Parameters ===--- Minimum Cycle Time (tCKmin) 0.833 ns Maximum Cycle Time (tCKmax) 1.600 ns Minimum CAS Latency Time (tAA) 13.750 ns Minimum RAS to CAS Delay (tRCD) 13.750 ns Minimum Row Precharge Delay (tRP) 13.750 ns Minimum Active to Precharge Delay (tRAS) 32.000 ns Minimum Active to Auto-Refresh Delay (tRC) 45.750 ns Minimum Recovery Delay (tRFC1) 350.000 ns Minimum Recovery Delay (tRFC2) 260.000 ns Minimum Recovery Delay (tRFC4) 160.000 ns Minimum Four Activate Window Delay (tFAW) 21.000 ns Minimum Row Active to Row Active Delay (tRRD_S) 3.300 ns Minimum Row Active to Row Active Delay (tRRD_L) 4.900 ns Minimum CAS to CAS Delay (tCCD_L) 5.000 ns Minimum Write Recovery Time (tWR) 15.000 ns Minimum Write to Read Time (tWTR_S) 2.500 ns Minimum Write to Read Time (tWTR_L) 7.500 ns ---=== Other Information ===--- Package Type Monolithic Maximum Activate Count Unlimited Post Package Repair One row per bank group Soft PPR Supported Module Nominal Voltage 1.2 V Thermal Sensor TSE2004 compliant ---=== Physical Characteristics ===--- Module Height 19 mm Module Thickness 2 mm front, 2 mm back Module Reference Card ZZ ---=== Manufacturer Data ===--- Module Manufacturer SK Hynix DRAM Manufacturer SK Hynix Manufacturing Location Code 0x01 Manufacturing Date 2018-W28 2018-W28 2018-W28 2018-W28 2018-W16 2018-W28 2018-W28 2018-W28 Assembly Serial Number 0x72446CE5 0x72446C05 0x72446AE9 0x72446A98 0x72189C5D 0x72446CE7 0x72446B14 0x72446C0A Part Number HMA82GU8AFR8N-UH Number of SDRAM DIMMs detected and decoded: 8 root@noah:~# od -Ax -t x1 -v /sys/bus/i2c/drivers/ee1004/0-0050/eeprom 000000 23 11 0c 02 85 21 00 08 00 60 00 03 09 0b 80 00 000010 00 00 07 0d f8 0f 00 00 6e 6e 6e 11 00 6e f0 0a 000020 20 08 00 05 00 a8 1b 28 28 00 78 00 14 3c 00 00 000030 00 00 00 00 00 00 00 00 00 00 00 00 0c 2c 15 35 000040 15 35 0b 2c 15 35 0b 35 0b 2c 0b 35 15 36 00 00 000050 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 000060 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 000070 00 00 00 00 00 00 9c b5 00 00 00 00 e7 d6 da 74 000080 04 11 1f 01 00 00 00 00 00 00 00 00 00 00 00 00 000090 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000a0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000b0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000c0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000d0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000e0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 f1 05 000100 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 000110 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 000120 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 000130 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 000140 80 ad 01 18 28 72 44 6c e5 48 4d 41 38 32 47 55 000150 38 41 46 52 38 4e 2d 55 48 20 20 20 20 00 80 ad 000160 ff 54 44 38 37 4e 35 32 32 36 49 30 31 00 00 00 000170 01 00 00 00 00 00 00 02 00 00 00 00 00 dd 00 00 000180 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 000190 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0001a0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0001b0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0001c0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0001d0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0001e0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0001f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 000200 Save to a txt file and open with Thaiphoon Burner (File, Open from Clipboard/File):

😁😁 😁😁 😁😁 😁😁 😁😁 😁😁 😁😁 😁😁 😁😁 😁😁 😁😁 😁😁

Oh, hey awesome. I didn't realize I could get to menuconfig (that's all I needed to know 🙂. I do lot's of work in OpenWRT). I assume this will be over a VNC connection to the container? EDIT: RTFM 🙂 "'docker exec -ti Unraid-Kernel-Helper /bin/bash'"