raujaku
-
Posts
18 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by raujaku
-
-
1 hour ago, Squid said:
You've got some modification / script
May 12 14:30:01 Loki docker: RAM-Disk synced
First thing to do is get rid of this, reboot and then try again.
I don't know of any modifications/script that I made or were to even get rid of that? I checked /etc/rc.d/rc.docker since right after it starts the ram-disk is synced and the only mention in that file is "DOCKER_RAMDISK=true."After checking the log and noticing the sync every 30 minutes a search found this.
I've removed it, rebooted and will wait to see if a nother container flips out.
-
Each time I use the Update All docker button, it fails to remove the container stating that the container is already in use.
giving a server error. Then I have a ghost container that refuses to be removed.
I have tried deleting the docker.img and rebuilding but the problem keeps re-occuring. The only way of removing the containers is by doing a full restart on the server. The shutdown then hangs when it's trying to unmount the drives. Eventually this leads to a dirty shutdown. Once the server is back up, then the command "docker rm --force "container" " works.
-
On 12/19/2021 at 8:59 PM, ThatTallGuy21 said:
Any word if you're able to patch this vulnerability? - @Knoxie89
Unfortunately, I'm going to have to remove this container if not or I get no response, just to be safe, which is disappointing because I really like the concept of this tool, and appreciate your hard work on it.
A new update got pushed today which contains the fix for log4j. Warning though, some still consider the "fix" to be more of a Band-Aid with the potential for the exploit to still exist.
-
This container contains the Log4j library which has been found to have an RCE exploit.
-
This container contains the Log4j library which has been found to have an RCE exploit.
-
On 4/14/2021 at 3:08 PM, Andiroo2 said:
On my system, HW transcode only breaks for tone mapping enabled 4K HDR files. Can you check on your end too? Is HW transcode working for other file types?
HW will work without tone mapping but what's the point lol? I'm currently on a version plex:version-1.22.0.4163-d8c4875dd. The newest plex update had broken HW transcoding for comet and rocket lake cpus.
-
27 minutes ago, Taddeusz said:
I’m updated to the latest version and QuickSync is still working for me. I have an i5 8400. I’ve seen people having issues with Intel’s 11th gen CPU’s and 4K HDR files.
Your right, after going past version-1.22.0.4163-d8c4875dd I can no longer transcode 4k HDR.
This is on a server using a w1290-P.
-
Don't know if this has been mentions yet but, quicksync stops working after version 1.22.0.4163. I tested this across multiple containers, each with the same results.
- 1
-
In unbound when using SSL? when the hash.unraid.net url is set the web browser spits out DNS_PROBE_FINISHED_NXDOMAIN.Fixed it: private-domain: unraid.net needs to be added into the unbound conf file
- 1
-
Is there anyway to test it without having to add a new movie to our Plex libraries?
-
-
when I try to get wireguard to work the container just hangs at
qBittorrent process listening on port 8080
-
Would you be able to make an icon for the Lian Li PC-O11D XL case?
-
11 minutes ago, Gbcue said:
Ok, I've made a new /appdata/locast2plex folder and added the config.ini to that folder. How do I point the docker config in unraid to that folder?
The author is making updates to the github and dockerhub as we speak, I keep seeing updates in the unraid docker updates column.remove all path,ports,vars
add var debug = yes
add new path for config file
container path: /app/config.ini
Host Path: "wherever your config file is located"
remove and re add the tuner in plex.
- 1
-
You'll have to make one
-
The container just updated to v5.0.
You will need to create a config.ini file ( an example template is on the creators github) and you will need to map /app/config.ini to your created config.ini file to get it to work now.
-
You cant pass through the NVME through stubbing but you can use it by changing your vdisk path to your /dev/disk/by-id/(your-nvme) location.
- 1
[Support] kizaing - Kavita
in Docker Containers
Posted
Changing the font size, doesn't seem to work.