1 hour ago, UnraidTobias said:

Hi @grtgbln can you please provide a correct support-forum link in your gpt4all container and add an example on how to set it up properly? With a LLM as an example and a Frontend? That would be so helpful, probably for many of us,.... thanks so much in advance!

The support link on the template points to the GitHub page for GPT4ALL, which contains documentation about the project. Please direct your project-specific questions to those locations.

Hello.  Trying out your Automatic1111 container but I can't find where the webui.sh file is located.  I can see it inside the container via command line, but not inside of the appdata directory when I navigate through the unraid file system or a file browser.  Can you please advise where this and the rest of the data is located?  I assume its writing directly into docker.img directly without using the appdata folder...?

On 7/29/2024 at 10:16 PM, grtgbln said:

The support link on the template points to the GitHub page for GPT4ALL, which contains documentation about the project. Please direct your project-specific questions to those locations.

Hi, i found out, the issue on my side is, that the nvidia card i have is to old. So nvidia drivers do not get detected....but according to gpt4all github readme, a gpu is not needed at all.

 

Is there an option you could provide the container also without the nvidia/gpu requirment? Or optional? Or can you elaborate a bit about the background why this is necessary, please? Thank you

Edited August 4, 20241 yr by UnraidTobias

Can someone help me install LocalAI with AMD support?

 

I don't understand the instructions about adding devices and variables...

 

" For AMD GPU support, add "/dev/kfd" and "/dev/dri" each as a Device and add the required Variables: https://localai.io/features/gpu-acceleration/#setup-example-dockercontainerd"

 

Thanks!

10 hours ago, Krakout said:

Can someone help me install LocalAI with AMD support?

 

I don't understand the instructions about adding devices and variables...

 

" For AMD GPU support, add "/dev/kfd" and "/dev/dri" each as a Device and add the required Variables: https://localai.io/features/gpu-acceleration/#setup-example-dockercontainerd"

 

Thanks!

not possible. the models won't use the amd gpu.

I recommend using the AIO gpu hib version:

localai/localai:latest-aio-cpu

to add the gpu if any for amd to a docker.

 

--device=/dev/dri --device=/dev/kfd

add the above to the extra parameter option:

 

I see they finaly updateed and fixed it.

Edited August 10, 20241 yr by bmartino1
redaction.

Hi, i managed to get the anythingallm docker image running. It works fine for RAG tasks, however i have an issue with attching URL's via the bulk web scraper. I see the following error in the log.

[collector] info: Discovering links...
[collector] error: Failed to get page links from https://learn.microsoft.com/en-us/azure/well-architected/reliability. Error: Failed to launch the browser process!
[1006:1006:0810/184605.831237:FATAL:zygote_host_impl_linux.cc(127)] No usable sandbox! Update your kernel or see https://chromium.googlesource.com/chromium/src/+/main/docs/linux/suid_sandbox_development.md for more information on developing with the SUID sandbox. If you want to live dangerously and need an immediate workaround, you can try using --no-sandbox.

Any help would be appreciated

14 minutes ago, EvilOni said:

Hi, i managed to get the anythingallm docker image running. It works fine for RAG tasks, however i have an issue with attching URL's via the bulk web scraper. I see the following error in the log.

[collector] info: Discovering links...
[collector] error: Failed to get page links from https://learn.microsoft.com/en-us/azure/well-architected/reliability. Error: Failed to launch the browser process!
[1006:1006:0810/184605.831237:FATAL:zygote_host_impl_linux.cc(127)] No usable sandbox! Update your kernel or see https://chromium.googlesource.com/chromium/src/+/main/docs/linux/suid_sandbox_development.md for more information on developing with the SUID sandbox. If you want to live dangerously and need an immediate workaround, you can try using --no-sandbox.

Any help would be appreciated

Simlar coding...

Any way, per the error,
as it appears that the Browser Error at launching chromium...

While I'm not familiar with what the anythingallm docker is nor its capabilities, if its web scraping, you may need to do something similar to collect the data.

I found it easier to use python  selenium with chrome installed
 

from selenium import webdriver
from selenium.webdriver.common.by import Byfrom selenium.webdriver.support.ui import WebDriverWaitfrom selenium.webdriver.support import expected_conditions as EC

and called:
 

 chrome_options = webdriver.ChromeOptions()
    chrome_options.add_argument('--headless')
    chrome_options.add_argument('--no-sandbox')
    chrome_options.add_argument('--disable-dev-shm-usage')

to launch the browser.

You may need similar settings...

Edited November 29, 2025Nov 29 by bmartino1
spelling/gramar

@bmartino1

 

Ok i figured out the problem. You need to add an argument to extra parameters of the docker container settings.

--cap-add SYS_ADMIN

 

This is referenced in the AnythingLLM documentation, so the author should probably include this as part of the instructions.

 

 

https://docs.anythingllm.com/installation/self-hosted/local-docker#recommend-way-to-run-dockerized-anythingllm

Edited August 13, 20241 yr by EvilOni

58 minutes ago, EvilOni said:

@bmartino1

 

Ok i figured out the problem. You need to add an argument to extra parameters of the docker container settings.

--cap-add SYS_ADMIN

 

This is referenced in the AnythingLLM documentation, so the author should probably include this as part of the instructions.

 

 

https://docs.anythingllm.com/installation/self-hosted/local-docker#recommend-way-to-run-dockerized-anythingllm

Thanks for diagnosing the issue, I have updated the template accordingly.

For the Invoke-AI container the path to models and outputs can be mapped elsewhere. Assuming your storage is fast or you have extra NVMe laying around.

The paths are:
- Container Path: /invokeai_root/outputs
- Container Path: /invokeai_root/models

Edited August 18, 20241 yr by TheFullTimer
removed markdown formatting

Hi,

the Invoke-AI container is pulling 4,5GB with every update almost every next day.
Do all these big files really change everytime there is an update or ist this a misconfiguration in the docker build file?

 

Cheers, d.

3 hours ago, disco4000 said:

Hi,

the Invoke-AI container is pulling 4,5GB with every update almost every next day.
Do all these big files really change everytime there is an update or ist this a misconfiguration in the docker build file?

 

Cheers, d.

I doubt the underlying dependencies are actually changing, but part of the Dockerfile build file is importing things like NVIDIA SMI and PyTorch on every build, without caching these layers, which unfortunately leads to having to redownload these base layers every time the image updates.

 

https://github.com/invoke-ai/InvokeAI/blob/5eb919f6020118764b8b5ece4f7660bd31f52472/docker/Dockerfile#L36
 

Edited September 8, 20241 yr by grtgbln

On 9/9/2024 at 2:45 AM, grtgbln said:

I doubt the underlying dependencies are actually changing, but part of the Dockerfile build file is importing things like NVIDIA SMI and PyTorch on every build, without caching these layers, which unfortunately leads to having to redownload these base layers every time the image updates.

 

https://github.com/invoke-ai/InvokeAI/blob/5eb919f6020118764b8b5ece4f7660bd31f52472/docker/Dockerfile#L36
 

Its also moved to the Pre-release branch now, is this expected behavior?

On 9/12/2024 at 12:48 AM, MrTroll said:

Its also moved to the Pre-release branch now, is this expected behavior?

It's set up to pull whatever the InvokeAI team deems the "latest" Docker image: https://github.com/invoke-ai/InvokeAI/pkgs/container/invokeai/273561071?tag=latest

The Local.ai container isn't working properly for processors that don't have AVX2 support.  From my understanding, there is supposed to be a feature that chooses AVX or AVX2, but this isn't happening.  So, one of the issues is that models won't load.  Not sure if this can be fixed from the image, or if this is an upstream issue for Mudler and Local.ai.  

 

 

5 hours ago, xer01ne said:

The Local.ai container isn't working properly for processors that don't have AVX2 support.  From my understanding, there is supposed to be a feature that chooses AVX or AVX2, but this isn't happening.  So, one of the issues is that models won't load.  Not sure if this can be fixed from the image, or if this is an upstream issue for Mudler and Local.ai.  

 

 

Looking at that thread, it seems like it's an upstream issue with the source code/image, not a problem with the Docker container.

Edited September 19, 20241 yr by grtgbln

On 4/24/2024 at 1:37 PM, BillyJ said:

 Need to chown -R nobody:users /path/to/anythingllm dir and then do the newperm command . Well that fixed it for me. 

thanks alot for your help.  this work for me even when i did the same through the file manager. but only the command line works.       chown -R nobody:users /mnt/user/appdata/anythingllm/

hi, how to add p2p or federaded paramter on template ?

i have tried in "extraparameters"

 

worker p2p-llama-cpp-rpc

 

but the container is crashing violently, same problem if y try to set federated mode in extra parameters

any idea ?

 

thanks

I am trying to install LocalAI with GPU support, but I get "Error: unauthorized: authentication required."  I can install the default/latest branch, but I get the same error on all of the other branches.  Help please.

Screenshot 2024-10-02 at 5.28.31 PM.pdf

for the prerolls, I'm getting an error for no file or directory.  I have the config file in that path so I'm not sure why it does not see it. 

On 10/10/2024 at 9:06 AM, animeking1987 said:

for the prerolls, I'm getting an error for no file or directory.  I have the config file in that path so I'm not sure why it does not see it. 

Inside the container, the config file is stored in "/config/". May I ask why you are manually running the script console'd into the container? The cron job should handle running the script automatically.

I tried installing the PinePods docker but i get this error.
I used postgres as db.

 

wait-for-it.sh: strict mode, refusing to execute subprocess
chown: unknown user/group Debian-exim:Debian-exim
chown: unknown user/group Debian-exim:Debian-exim
Error: Format string 'DB_TYPE=%(ENV_DB_TYPE)s,SEARCH_API_URL=%(ENV_SEARCH_API_URL)s,DEBUG_MODE=%(ENV_DEBUG_MODE)s' for 'environment' contains names ('ENV_SEARCH_API_URL') which cannot be expanded. Available names: ENV_API_URL, ENV_APP_ROOT, ENV_DB_HOST, ENV_DB_NAME, ENV_DB_PASS, ENV_DB_PASSWORD, ENV_DB_PORT, ENV_DB_TYPE, ENV_DB_USER, ENV_DEBUG, ENV_DEBUG_MODE, ENV_EMAIL, ENV_FULLNAME, ENV_HOME, ENV_HOSTNAME, ENV_HOST_CONTAINERNAME, ENV_HOST_HOSTNAME, ENV_HOST_OS, ENV_PASSWORD, ENV_PATH, ENV_PINEPODS_PORT, ENV_PROXY_PROTOCOL, ENV_PWD, ENV_REVERSE_PROXY, ENV_SHLVL, ENV_TZ, ENV_USERNAME, ENV__, group_name, here, host_node_name, numprocs, process_num, program_name in section 'program:client_api' (file: '/pinepods/startup/supervisord.conf')

18 hours ago, UnraidUser71374 said:

I tried installing the PinePods docker but i get this error.
I used postgres as db.

 

wait-for-it.sh: strict mode, refusing to execute subprocess
chown: unknown user/group Debian-exim:Debian-exim
chown: unknown user/group Debian-exim:Debian-exim
Error: Format string 'DB_TYPE=%(ENV_DB_TYPE)s,SEARCH_API_URL=%(ENV_SEARCH_API_URL)s,DEBUG_MODE=%(ENV_DEBUG_MODE)s' for 'environment' contains names ('ENV_SEARCH_API_URL') which cannot be expanded. Available names: ENV_API_URL, ENV_APP_ROOT, ENV_DB_HOST, ENV_DB_NAME, ENV_DB_PASS, ENV_DB_PASSWORD, ENV_DB_PORT, ENV_DB_TYPE, ENV_DB_USER, ENV_DEBUG, ENV_DEBUG_MODE, ENV_EMAIL, ENV_FULLNAME, ENV_HOME, ENV_HOSTNAME, ENV_HOST_CONTAINERNAME, ENV_HOST_HOSTNAME, ENV_HOST_OS, ENV_PASSWORD, ENV_PATH, ENV_PINEPODS_PORT, ENV_PROXY_PROTOCOL, ENV_PWD, ENV_REVERSE_PROXY, ENV_SHLVL, ENV_TZ, ENV_USERNAME, ENV__, group_name, here, host_node_name, numprocs, process_num, program_name in section 'program:client_api' (file: '/pinepods/startup/supervisord.conf')

This sounds like an issue with the app itself. Please reach out to the appp developer directly.

6 hours ago, grtgbln said:

This sounds like an issue with the app itself. Please reach out to the appp developer directly.

Are you sure? because this error seems like an error of the parameters passed to docker.
For you it worked when you configured to use postgres?

On 10/15/2024 at 11:00 AM, UnraidUser71374 said:

I tried installing the PinePods docker but i get this error.
I used postgres as db.

 

wait-for-it.sh: strict mode, refusing to execute subprocess
chown: unknown user/group Debian-exim:Debian-exim
chown: unknown user/group Debian-exim:Debian-exim
Error: Format string 'DB_TYPE=%(ENV_DB_TYPE)s,SEARCH_API_URL=%(ENV_SEARCH_API_URL)s,DEBUG_MODE=%(ENV_DEBUG_MODE)s' for 'environment' contains names ('ENV_SEARCH_API_URL') which cannot be expanded. Available names: ENV_API_URL, ENV_APP_ROOT, ENV_DB_HOST, ENV_DB_NAME, ENV_DB_PASS, ENV_DB_PASSWORD, ENV_DB_PORT, ENV_DB_TYPE, ENV_DB_USER, ENV_DEBUG, ENV_DEBUG_MODE, ENV_EMAIL, ENV_FULLNAME, ENV_HOME, ENV_HOSTNAME, ENV_HOST_CONTAINERNAME, ENV_HOST_HOSTNAME, ENV_HOST_OS, ENV_PASSWORD, ENV_PATH, ENV_PINEPODS_PORT, ENV_PROXY_PROTOCOL, ENV_PWD, ENV_REVERSE_PROXY, ENV_SHLVL, ENV_TZ, ENV_USERNAME, ENV__, group_name, here, host_node_name, numprocs, process_num, program_name in section 'program:client_api' (file: '/pinepods/startup/supervisord.conf')

This is a docker permission error seen from with in postgress where it attempted to docker permission set a crown

Please ensure that your post gress folder located on unraid has docker safe permission applied..

cd /mnt/user/appdata/postgress docker data
chmod 777 -R *
chown nobody:nogroup -R *

You may alos need to run uuid guid as 99 100


to fix docker host file write access for the database.