Everything posted by dee31797
-
Virt-Manager, Intel-GPU-Tools and more Dockers
no that should be something else, unless you've manually changed it in the settings where the option "Container Path: /config" appears. I'm at a lost on what's causing this issue for you. The beauty of docker is that once the image is setup and works, you can put it anywhere docker is running and get the same results. If the Binhex container is working for you then I have no choice than to recommend it.
-
Virt-Manager, Intel-GPU-Tools and more Dockers
Sometime is preventing the Krusader app from starting inside the container and the only thing I can think of that could do that is old/corrupt stuff in the appdata/krusader folder. In the log you're not getting the messages about the app starting [services.d] starting app... [app] starting Krusader... [services.d] done. ... ... ... ...
-
Virt-Manager, Intel-GPU-Tools and more Dockers
I can't see the name from your first screenshot, but the default name (that should match the template name) is krusader lower case.
-
Virt-Manager, Intel-GPU-Tools and more Dockers
This is a tough one. I started up a fresh krusader container on my test system with your settings and it starts right up. It's a long shot I think, but lets try to first remove the container by clicking the krusader Icon then remove. After that delete the folder /mnt/user/appdata/krusader. Lastly, once the folder is gone go back to the docker tab, add container, select template Krusader. Let me know if it makes a difference.
-
Virt-Manager, Intel-GPU-Tools and more Dockers
Thanks, your settings are pretty much identical to mine. You are accessing the Krusader through a web browser using http://<yourUnraidIP>:6080 ? If you, can you also add the logs? The logs are available in the docker tab, white button far right.
-
Virt-Manager, Intel-GPU-Tools and more Dockers
Please attach the settings for the krusader container from the Unraid GUI
-
Virt-Manager, Intel-GPU-Tools and more Dockers
No, the process is completely manual. You have to map the comskip.ini and the folder containing the videos (example from previous post) and manually tell comskip what/where video file you want it to use.
-
Virt-Manager, Intel-GPU-Tools and more Dockers
Unfortunately auto-comskip is setup to just do it's thing. Watch for videos files and automatically remove commercials. If you have the desire and command line and docker skills, you can do it manually with my other docker image djaydev/comskip. From the command line run: docker run --rm -ti -v "/YOURFOLDER/comskip.ini":"/opt/comskip.ini" -v /YOURVIDEOFOLDER/videos:/videos --entrypoint='bash' djaydev/comskip Using vprj requires a custom comskip.ini, so set that up and map it, replacing "YOURFOLDER" with where ever you saved your comskip.ini settings file. After running that docker command you'll be at a command line prompt to run a manual process of video to vprj. bash-5.0# Usage: comskip [-h|--help] [-w|--debugwindow] [-n|--playnice] [--zpcut] [--zpchapter] [--scf] [--videoredo] [--videoredo3] [--csvout] [--quality] [--plist] [-m|--demux] [--hwassist] [--cuvid] [--vdpau] [--dxva2] [--decoders] [--threads=<int>] [-p|--pid=<string>] [-t|--ts] [-d|--detectmethod=<int>] [-v|--verbose=<int>] [-u|--dump=<int>] [-s|--play] [--timing] [-q|--quiet] [--ini=<file>] [--logo=<file>] [--cut=<file>] [--output=<file>] [--output-filename=<file>] [--selftest=<int>] <file> [<file>] I've never used vprj so I can't help with the exact command(s) you'll need to use for comskip.
-
Virt-Manager, Intel-GPU-Tools and more Dockers
dtctechs, I've added some downloads to uGet to test column sorting (I hadn't tried it before now) and I can't replicate the issue. I initially thought it could be browser incompatibility but it also works for me in direct VNC. Unfortunately the only suggestion I have is to delete the config folder and rebuild the container. The quickest way to rebuild the container is to force an update from the Unraid Dashboard WebGUI.
-
Virt-Manager, Intel-GPU-Tools and more Dockers
Hi, The first half of the process is motion detection and it will be the majority of your CPU usage. Motioneye uses the application "Motion" to detect changes in the video. The more camera feeds, the more CPU usage and it's all software based. Once motion is detected and motioneye is set to record video on said motion, Motioneye either encodes the video to a new video codec or you can use passthrough to save the video in the original codec. Encoding of the video can be done with a hardware device if available and supported. For hardware accelerated encoding you must pass a hardware device to the container. For example, V4L2M2M requires a hardware device that's typically located at "/dev/videoX" and must be mapped to the container. I've only seen V4L2M2M with ARM based SBC's such as the Odroid XU4 hardware accelerated encoding (reference https://github.com/ccrisan/motioneye/releases/tag/0.42). Other options supported by motioneye are Nvidia's NVENC (requires a Nvidia GPU) and Intel's QSV (requires an Intel iGPU apart of an Intel CPU). Even though ffmpeg has options such as VAAPI (also GPU based), Motioneye does not support it. Here's the catch, even if you do have a Nvidia GPU or Intel iGPU to map to this container, since this container image is based on Alpine linux it doesn't have support for it. So to use hardware encoding I recommend you use the docker container that's created by Motioneye's original author, located at https://hub.docker.com/r/ccrisan/motioneye . It's based on Ubuntu so it's 3 times the size of my container. I haven't tested it myself (I use passthrough video setting personally) but I believe his container does support hardware encoding. As we mentioned once you install his container you have to map a supported GPU to his container before hardware accelerated encoding will work.
-
Virt-Manager, Intel-GPU-Tools and more Dockers
No sorry it only removes commercials.
-
Virt-Manager, Intel-GPU-Tools and more Dockers
Which program do you speak of?
-
Virt-Manager, Intel-GPU-Tools and more Dockers
Thank you! Currently there's no options for the audio but I will look into adding something like that in the future.
-
Virt-Manager, Intel-GPU-Tools and more Dockers
click "clipboard" in the top right click text box, press ctrl + v on your keyboard to paste text you desire the container to have click submit in the uget wegui go to where you need the text, press ctrl + v on your keyboard to paste text you desire edit: the container is still usable with pasting text.
-
Virt-Manager, Intel-GPU-Tools and more Dockers
I can help with the file system, but you're going to have a tough time with this container. It's an advanced setup running a web server, dhcp server, text based configuration via config files. The docker container settings (in Unraid GUI) has a list of volumes, variables, devices, etc and are managed by you. In this specific instance you need to add "/etc/dhcp/dhcpd.conf" to the docker container. The most common why this is done is with an appdata folder, "/mnt/user/appdata/glasss-isc-dhcp/dhcpd.conf" mapped to "/etc/dhcp/dhcpd.conf", but the choice is yours use whatever host directory you desire. Once your selection is made, use the Unraid GUI docker settings to change the host path to your selection and the container path should already be filled in when you installed the container. For an more in depth explanation on docker settings and volumes please see https://wiki.unraid.net/UnRAID_6/Docker_Management
-
Virt-Manager, Intel-GPU-Tools and more Dockers
Yes, the directory exists on your machine, you access them however you wish. The docker container only sees them as a mapped volume. If not mapped from your machine to the docker container, then they don't exist.
-
Virt-Manager, Intel-GPU-Tools and more Dockers
I believe the issue that causes it to shutdown is the missing dhcp configuration file, log message "dhcpd-pools: parse_config: /etc/dhcp/dhcpd.conf: No such file or directory" WIthout this file the DHCP server will not start as well as glass admin. For a sample config file, see www.github.com/djaydev/docker-glass-isc-dhcp/blob/master/sample.dhcpd.conf
-
Virt-Manager, Intel-GPU-Tools and more Dockers
If the MakeMKV ripped DVDs are .ts files then Recordings-autoconverter will convert them. If they are not .ts files, you will have to use a different program like unmanic, handbrake, tdarr, or H265ize. I believe there are others but these I know for sure are in Unraid's CA Apps.
-
Virt-Manager, Intel-GPU-Tools and more Dockers
That's the same as my go file. What processor are you using? Also, the igpu has to be turned on in bios. Lots of variables to get igpu working in Unraid and this thread isn't the best place to figure it, I just put together the intel-tools container.
-
Virt-Manager, Intel-GPU-Tools and more Dockers
Until that's working this docker will be blank/black screen.
-
Virt-Manager, Intel-GPU-Tools and more Dockers
The app can't find the GPU for some reason. Goto the unraid cli console, type ls -la /dev/dri post the output here
-
Virt-Manager, Intel-GPU-Tools and more Dockers
logs: go to unraid dashboard, click docker icon, click logs
-
Virt-Manager, Intel-GPU-Tools and more Dockers
Please post the logs. The webui from your settings is port 7800, so goto http://yourunraidip:7800
-
Virt-Manager, Intel-GPU-Tools and more Dockers
Thanks for the feedback. I'm very sorry for the confusion. I wasn't saying you knew or didn't know, I was just saying why that temporary directory is not mapped to a volume by default. All I can do from here is acknowledge your feedback and offer assistant to you if you need/want it. Since you said you already mapped your /tmp directory on your system you are already good to go from that standpoint. Of course, the other obvious thing is to limit the amount of 4k videos you have in your source folder, and/or increase the docker image size.
-
Virt-Manager, Intel-GPU-Tools and more Dockers
Hi @frank-unr Thanks for the feedback. Since it's a temporary folder, I don't set it to a persistent volume by default, but I understand if you want to manually map it. My /tmp in the Handbrake docker is current 12KB of files.