bmartino1

this is why the recomendation to the lxc alternative as if you want rolling lattest updates... Docker lattest won't do any good here and can brick. (what would normaly be set for the curent lattest stable..) *Somethign we can sugest and ask 11 notes if they are willling to make a docker tag and with the lattst stables chang and set teh docker tag... with the release of unfi OS for a VM I would recemd runing a debain VM and ther unfi stack there any more... https://itadon.com/blog/unifi-os-server-self-hosting/ as it has to do with superviosr unifi docker stack and other where unfi wonlt let there stack run outside of podman supervisor and there weird sytem.... Docker is still great for network only. and light weigh qucik contorl center sytems.

I have finished updateing scripts notes configs and decided to go jitsi for video and voice. https://github.com/bmartino1/matrix-textvoicevideo I have tested this on mutiple sytems with a dns domain name. I have tested both video and voice. complete self hosted. to keep things simple I set coturn and jvb for jitsu video/voic connections to the host unraid lan ip. and the rest in its own compose contorled docker network... see coments in line with code... using docker nat form nginx bridge mode to router nat incoming 443 or 80 default http/https traffic though router NAT to talk to 60443 60080 for nginx RP ssl certs.... This leaves the livekit (organly i ran both cotrun and livkit as cotun is a TURN server and livekit also has a TURN server and the both conflcied as synapsoe is built to run wht cotrun but not the turn server withint livkit. Since elemnt will fallback to meet.jitsi public domain i decdied to add the abilt to use a slef host version. soemthing that i have tested and can gurante a spin up... data folder has example configs with in you can manual edit eh env and mathcc the data in it to teh needed items int eh configs to learn more about each docker setup and piece. *This includes nginx RP forwading settings turn use and how... (See readme) This is the best I can do to hlep facilate new user jumping in and to help some of my knownw friend gorups to quickly spin up a encrypted full functial matrix server.

while rocket.chat is still a failry decent choice. Iahve finshed my edits and testing on a good full self hosted veriosn 100% self hosted and free https://github.com/bmartino1/matrix-textvoicevideo I have finished wokring test to make a git clone setup run and done...

1st post picture your too far deep you need to mount /mnt/user/appdata/Plex-Media-Server As the Libray folder need shown... this should be the same as your appdata folder... https://forums.unraid.net/topic/196453-support-plex-db-repair-docker/#findComment-1601211 This is the only thing that needs set to run... the continer will then see /config/Library and things will work as intended... Its the only data I don't have that the end users must set. as you can see my appdata for plex is different and each docker is different for appdata... my scirpt will traverse into the databse folder folwing default folder nested...

that said this is now complete in a working stack for unraid compose... https://github.com/bmartino1/unraid-rocket.chat GitHubGitHub - bmartino1/unraid-rocket.chat: unraid setup sh to...unraid setup sh to help users run rocket chat. Contribute to bmartino1/unraid-rocket.chat development by creating an account on GitHub.a full stack setup to run via rocket.chat support recommendations... This will set up the mongdo, nats, rocket.chat and nginx https RP to run the application suit. Thats the best I can do until Rocket.chat fixes their documentation and finalizes / makes their decision on how they move forward. I personally am looking at other alternatives. As such, while not deleting the AIO, will no longer be able to maintain it... CA should see a removal of it soon... and there is no good way to add unraid ca tempatles for standalone setup... Again. Per Mainteiner, to get application support/updates, please use the Docker Compose method!

I was ther day one with truenas scale introductions and form what ehy were to what they are NOW, I woudl say STAY AWAY form Turenas!... Form breaking build updates to know code thievery and other issues with the sytem as a whole... Glosuter FS was the big one... TrueCharts helm dockers is what makes the sytem useable in the docker sense... Breaks upgrades... (Lookinto hex OS the Proper Web Interface for turenas as well) Paid web UI Overley Being blcoked form making root level edits and fixes... They still have a known issues with k3 and k8 and need to pick one or the other... They excel in 1 implementation only and that is a Pripertary setup of ZFS with proper web UI intergration for zfs zvol, zpool vdes etc... Evything else they have on teh truenas name is garbage... freenas was better, core is still good But I don't like to underline OS freebsd... (known kenreal.host level CVE still unpatched.. Scale was teh happy let get behind this and they said No to every dev activle blocked support features or kiled many sytems between build not once but 3 times due to ther base orchestration layer and "helper" Truenas should be avidod Unles you want full webUI zfs intergration and will not adventure outside of samba for staroge with ZFS ... vm intergration is still garbage, they borked samba, dockers are a mess and with proper open zfs iimplementations and intergratios there pripertary setup creates unecesay zpool swap paretion on disk SO NO If i were to recomend any alternative albit its por cons and what your tryign to do... Open Media Vault..

its more issues with how to continue to support what i'm willing to support and waht teh main project documenttion will allow... as explin in previous post the issues has and will always be isseus with the mong db. AIO - issues with to many moving parts and teh need of a RP (I'm not going to support a turn key for that... AIO - Will eventaul break due to changes on rocket.chat and tehre miss of documentations. Rocket.chat wnats it eitehred installed in a linux enviroment or run there compose stack. which i'm all for due to the nature of theere sytem. but htey are not 100% free either and I'm not fully wantign to support intergrations without dues... So the best I can do to assit users, new uesr to stay on track witht he rocket.chat mainteners is have users use compose... (info already shared on this post...) as I atempted to due CA seperate instances, a copose file in teh past and ended with a quick short term AIO solution. (atempted to have them support a AIO givein the changes they are workign on...) they refused... as they wanted teh code and teh authoship of every coponet that is used in there stack... (esental taking others works and legay stealing them with nor support form them and all legal algory on the dev... SO I'm against Rocket.chat for there S*** Practices and given what they were to what they are now and what they are tryign to do I DON"T RECOMEND THEM! Nor willign to support or try to support interaction on it.. since the AIO was more a proff of concept due to there BS of documentation and non of the rocket.chat stuff documented nor exmplained in such a way to run... So simalr to imich and other stacks where I will galdy assit where I can but ultimatle things built were built for my use and shared witht eh comunicty on what, how and why come... BUT! I still highly recomned running compose! https://github.com/bmartino1/unraid-rocket.chat To install and use rocket.chat per the mainteiners... (as I'm at teh will of what they will allow and support!) git clone https://github.com/bmartino1/unraid-rocket.chat.git \ /mnt/user/appdata/unraid-rocket.chat cd /mnt/user/appdata/unraid-rocket.chat chmod +x setup.sh ./setup.sh as again I don't have a good way to expalin and edit nor share a good turn key solution to docker stacks that require more then 1 docker and setup instance.. when it is easer to maintin and beter used per teh mainterners recomendation... so... Why Not AIO? The AIO (all-in-one) image bundled MongoDB, NATS, Postfix, and Rocket.Chat into a single container. While convenient, it had significant drawbacks: Update friction — MongoDB and Rocket.Chat update on different cycles. A single image meant rebuilding everything for any update. MongoDB replica set issues — Running mongod inside the app container led to PID management problems and unreliable replica-set initialization on Unraid. Debugging difficulty — All logs mixed together, health checks couldn't target individual services. Upstream drift — Rocket.Chat's own compose structure changed significantly (new NATS requirement, MongoDB 8 support, deprecated old compose files), making the AIO increasingly brittle. The multi-container approach lets each service use its official image, get independent updates, and fail/restart independently... Sorry But I'm esental done being peoples support...

when isntalling CA are you installing the cuda version? also folow the nvida plugin 1st post data: https://forums.unraid.net/topic/98978-plugin-nvidia-driver/#findComment-913251

while Ill leav the aio alone I will most likely not update it due to rocket.chat chagnes. that and I'm looking into a more free solution... so ill be workign more on a matrix setup as seen here: https://forums.unraid.net/topic/127917-guide-matrix-synapse-w-postgres-db-chat-server-element-web-client-coturn-voice/page/3/#findComment-1607898 and not be as much assistance for this rocket.chat docker. https://github.com/bmartino1/matrix-textvoicevideo

this is a nice guide. I'm still ironing out some kinks but have a semai decent setup here https://github.com/bmartino1/matrix-textvoicevideo where you git clone cd /mnt/user/appdata git clone https://github.com/bmartino1/matrix-textvoicevideo.git Run the automated script... ./setup.sh --domain chat.yourdomain.com *I used a afraiddns sub domain name https://freedns.afraid.org/ then setup docker compose point to your github download folder. docker compose example: editing the stack AFTER THE SCRIPT RUN! proff of concept: using: docker exec -it matrix-synapse \ register_new_matrix_user \ -k "synapse-homeserver.yaml config shared registrationkey" \ http://localhost:8008to make users... By al means its not perfect. *I have adatinal thigns I don to my compos files... But this should help alevate concerns/ questions on making a turn key run and done... while voice and viode work i'm having a hard time geting them to function. I can then use the element web app for phone / browser... https://element.io/en/download given alot of users looking for discord alternatives...

FYI if users also run the FCP plugin (Fix common problems) its is normal to see plugins that are not in the CA yet and warnings and errors here. this will go away once we finish working with Squid to add chodeus plugin https://raw.githubusercontent.com/chodeus/folder.view2/main/folder.view2.plg added to the ca. @Squid thoughts on how to add an extension or update current CA? To install, paste the link at the plugin install plugin tab and Force install it. (I had to run with force due to CA folder view 2 plugin in CA. that may be causing some conflicts.)

Thank you very much sir! This is awesome.

you need to chose to have it for the VM only or for unraid host access and dockers... VFIO bind removes it form the host to never be seen or used by unraid host or dockers... VFIO bind is correct adn prper way to pass a gcard to a VM. to unbind a gcard this way you must unbind the GPU form VFIO and REBOOT UNRAID! THE VM WILL NOT BE ABEL TO BE USED WITH BOTH! its one or the other... This is wher vgpu unlock and other hackery came about... amd mxgpup and Windows NVIDIA GPUP... This is not a support feature nor operation on unraid slackware linux. SO first pick do you want the G Card for the VM or for the unraid Host...

can be run via docker compose: https://github.com/Gururagavendra/gmail-cleaner/blob/main/docker-compose.yml looks to be only one app and requires google auth token... more on the core of the applicaiont. # Uncomment and set OAUTH_HOST if accessing via custom domain or server IP # - OAUTH_HOST=gmail.example.com # Uncomment and set OAUTH_EXTERNAL_PORT if using custom port mapping # (e.g., if you map ports like "18767:8767", set OAUTH_EXTERNAL_PORT=18767) # - OAUTH_EXTERNAL_PORT=18767 Gmail supports this with the web UI. I don't see the need to run a 3rd party application that will read and have access to my email account... https://support.google.com/a/answer/2368132?hl=en

Most dockers in compose are not taged lattest adn are instaed taged to that docker. I have found when set to lattest taht squids CA auto update can targe and update the docker. This downlaods the image the compse stack needs rebooted... Login once a month and hit update stack button or pull the script thte button does and add to a a user script... for instance: If I want to update the ars dockers since this is my latest tags.. reveres enginer the code page.. <input type="button" value="Update Stack" class="update-button" id="update-ARS-Stack" onclick="UpdateStack(&quot;/boot/config/plugins/compose.manager/projects/ARS-Stack&quot;);"> root@BMM-Tower:/boot/config/plugins/compose.manager/projects and target xyc and there comand.. Or do what I do... as I set the copose file at a specal location. each docker gets a pul poloicy line: The command-line options are: --pull always --pull missing --pull never Using the command line option will override any pull_policy specified in the Compose file for that particular command execution. per docs: https://docs.docker.com/reference/cli/docker/compose/up/ https://docs.docker.com/reference/cli/docker/image/pull/ https://stackoverflow.com/questions/64493477/docker-pull-image-policy-settings#:~:text=As%20far%20as%20I%20know,run%20act%20like%20imagePullPolicy:%20Always%20 And runa a user scipt to call docker-comse down /pathto the copse file and compse up the compose file and let at startup update teh docker images.

no, there is a support post area where someone uses a user scirpt and grabs the latters salkc package to install v5 not part of the stable plugin... root@BMM-Tower:~# docker-compose -v Docker Compose version v2.40.3 root@BMM-Tower:~# that saicc primeeval_god has kept this uptdate. example as unraid runs lsack ware linux: http://www.slackware.com/~alien/slackbuilds/docker-compose/build/docker-compose.SlackBuild and per the change, the last long version I know was v2.35 There is a difference between Compose v5 and the command docker compose and what Slackware Linux builds with docker for dcoker-compose... Docker Compose does not have a "v5" release; the current major version is v2, used with the docker compose command. It can be installed on Slackware Linux using the manual binary installation method or the SlackBuilds repository. So Do so at your own risk...https://docs.docker.com/compose/install/linux/#:~:text=To%20download%20and%20install%20the,$%20docker%20compose%20version

You're killing me here :/ ... I can't type to save my life... correct I can't make it any simpler as I can't preset data I don't know... and don't have full data here no other info that i can use to fully clairfy and I can't assist anymore... GO ASK AI! Also things your asksing are outlined in the template! Outlined Here mutiple times and expalined on the DOkcer hub and the unraid suprot post... So I don't understand nor get your confusion... and IDK what your doing outside of not asking clear cut question... or not folwing basic instructions... too braod... not specfic enouth... I don't know if you didn't use a template default data path to the plex media folder that contins the database files... PLEAS POST THE APPDATA FOLDER FOR YOUR PLEX FOLDER AND WHAT DOCKER IAMGE YOUR RUNNIGN!!!! IDK which plex is your main plex IDK wher your data is And I don't need to know... POST A DAM DIAG FILE!!! some one else will assit... I don't know how your runnign plex. There are Many plex dockers. I prefer linuxserver per example... Your caught up on a non problem due to the nature of how i programed the docker and the template based on a recomendation to supply what ever your plex dokcker repository docker image is... AND are in advacne seeting chaign things you shouldn't SO AGAIN! So the plex match is litelr a "filter" of words to find what the filter catches and dockers to kill so the plex docker to ensure it is stoped. AS YOU WILL BREAK PLEX IF ITS ON AND THIS CONECT TO THE DATBASE TO REPAIR!!! ALL it does, by this setting islooking for anything with "plex" per docker ps and KILL IT! so no plex is NOT running! as my docker hub image/repoiostoy https://hub.docker.com/r/bmmbmm01/plex-dbrepair the unraid temaptel based on your edits NEEDS TO BE DESTORYED AND INSTALLED default settings... with only 1 change... SEE SUPPORT!: https://forums.unraid.net/topic/196453-support-plex-db-repair-docker/#findComment-1601211 based on the unraid tmplate I've done a lot of YOu can't mess this up scripting in this docker... As IT will auto map the unraid docker sock to connect to be able to kil dockers, This will auto filter and kill any and all things named plex (with safe guards to not killl itself as the dbrepair image is called plex-dbrepair)... This will auto run the dbreapir automatic unless you change the variables... LIKE DID YOU EVEN READ THE ORANGE! or tempate settings... just set the appdata and click apply this auto does EVERYTHING FOR YOU! You ONLY AND just need to set the DB folder to the plex Libray folder... thats it... PER YOOUR POST AND DATA HERE this should be: /mnt/user/appdata/Plex-Media-Server Otherwise YOU HAVE A DIFFENT DAT PATH TO THE DATABASE! SO RECAP!!! DEFUALT TEMPTE INSTALL CHANGE ONLY THIS!!! AND NOTHING ELSE! CLICK APPLY then open the docker/ continaer log of dbrepair... as THIS RUNS THE SCRIPT AND DBREPAIR APP!!!! LET it finish... dbreapir automaticaly will run and repair the plex database... See LOG THAT IT! I litterly can't make it any simpler.... Ialso Can't gurantee a dbrepair will fix your isseus given basic docker and unraid tempatle setups... given teh issues here... To assist further, I will not be back... Please Post the docker your trying to repaire SCREENSHOTS! and MY DOCKER LOGS based on the log I can infomr you what happened....! Then i can assit further... as You shouldn't have to supply the plex OR EDIT THE repo... its recomen so only that gets killed. as if you have plex or if plex is in any other docker this Docker will KILL THEM! That all https://youtu.be/URXvnFnlUeE?si=yBVbU6tk2zr-N8dS

step 2 is optional stop trying to set it if you don't know...

the issue you have atm is your calling a plex docker image and not my docker image: you may need to delte your cuirent tempate and reinstall per teh CA Docker template: go to select teh template: and hit the x to remove the tempalte: then go to the apps page and install... Your making this more complcated then it actual is...

either or pick one. this is how my docker identifes the plex continer. by default it will search unraids dockers for anythign conting plex I recomend using the repository image as its a direct this one and kill.

I see whats going on now... appologies for my over sight i didn't see what you rarly had on screen shot.. as in thoery the only thing you frealy have to do is add teh appdata folder to the plex Library and click apply no other chnages should be necessay to run a automatic repair... what I recomend is opening 2 web pages in unraid... this way we can grab the data needed... so in one page be at teh dm repair install page noted on teh left. and edit your plex docker to grab the needed data form the right... example: Step 1 set the Plex folder path: OPTIONAL / Recomend step 2 set the container name or image OR thats it... run my docker dbrepair...

the repositoy it self is wrong you don't change the repository at the top that the docker tag you pull bmmbmm01/plex-dbrepair repostiry should never change.. That repository needs to go here: replace plex with the repository tag you have...

yes, looks good if you cd /mnt/user/appdata/Plex-Media-Server and run command ls to list the contents You should see a "Library" folder. If yes, then that's correct! root@BMM-Tower:/mnt/vm-zfs/Dockers/Plex/database# ls DBRepair.sh* Library/ root@BMM-Tower:/mnt/vm-zfs/Dockers/Plex/database#

with compose we can add all kinds of lables and test things. we can also add -l folder.view2.icon: 'https://path.to.icon.png'" to extra parm in a unraid tempalte to add adatainl things to teh exisitng unraid temaptle so not a compose only feature... Most lables are harmless and are usualy used with conjuntion with other dockers. example watch tower has a label settings -l com.centurylinklabs.watchtower.enable: "true" then wath towe will use the lable. Tailscale with tsdproxy has label settings Example my immich: like, labels read from the folder view is the correct way to interpret what is doing what. and can be interchanged using compose to docker run and docker run to compopse. docker run to compose https://www.composerize.com/ compose to docker run: https://www.decomposerize.com/ Ten having a unified label that the other dev have already made. dockerman for CA composeman for Compose plugin... we just have to have documentation of lables is all.