aptalca

Long time Plex issue. Report it to them

Too many users, the well dried up 😅

You bring up an interesting point I had not considered. s6 supervisor executes the init files in alphabetical order. The custom files in that folder are executed by a script named "99-custom-files" and the python3 docker mod creates an init file named "99-python3" and that's why your custom file is executed before python3 installation. I guess I'll have to update all the mods to use "98-blah" so they execute before the custom files. Until then, restarting the container should fix it for you because on second start, pip will already be installed when your custom file runs.

If you set it to only one gpu's id, f@h will still see both gpus, but it won't be able to start the job on one of them. You'll see an error in the log, something like " no compute devices matched gpu #0 blah blah you may need to update your graphics drivers". I paused that gpu so it no longer receives jobs it won't be able to complete.

Did you read my linked thread above? Post a full log, post your docker run and check the openvpn log in the config folder

Because openvpn-as got an update and they changed some things Check the openvpn logs in the config folder

I tested with 2 gpus and it works There's a screenshot of it in this article: https://blog.linuxserver.io/2020/03/21/covid-19-a-quick-update/ By the way, you don't need to edit the config at all (in fact, don't). If you allow both gpus via nvidia arguments, they'll both be used automatically.

Try an incognito window

You forgot "--runtime=nvidia"

Doesn't pgadmin listen on port 80?

The container by default doesn't have any projects enabled or even added. It doesn't do anything until the user sets it all up in the webgui. The user is expected to set it up the way they prefer. Also, it comes with all original boinc default settings. We don't modify anything.

Folding@home works with amd gpus, however, we do not support it with this image. Simply because none of us have a suitable test environment. I have one amd gpu, but it crashes my unraid servers when I try to pass through to a Linux VM. I don't believe there currently is a way to install necessary amd drivers on unraid for use in containers, but again, my knowledge on amd in containers is not very deep.

Jobs are distributed server side. We have no control over it. They may have different priorities based on cpu size, gpu type, etc.

F@H does not support Intel gpus

With docker compose you can. Anyway, that was just an option listed, not a recommendation. For the second, you need to look at docker faqs. It's an unraid thing but in a nutshell, you use the key/value to set the variables and you can add as many as you like (volume mappings, too).

You can ask their dev Map the file somewhere (or use docker secrets) and pass the location in an environment variable

This is what we use with our letsencrypt image: https://github.com/linuxserver/reverse-proxy-confs/blob/master/code-server.subdomain.conf.sample

Yup, any disease will prioritize covid-19 It looks like the servers are overloaded and it may be a while before you're assigned a job

Haven't seen that. Try deleting it manually?

Don't quote me on this, but I believe this container uses the main gpu cores whereas plex/emby/jellyfin use a separate dedicated hardware video acceleration core. So they shouldn't compete for the same resource (except for maybe ram, but this container uses little) Same way live streaming does not degrade the gaming experience as the livestream part uses the dedicated video acceleration core.

@CyberMew I don't know how much you used code-server, or vscode for that matter, but when you open a terminal, you have access to the entire container. Same as when you open the terminal on a bare metal install of vscode, you have access to the entire machine contents. So I genuinely don't understand what your expectations are here.

What? Not expose to what or who? It's the folder that contains the container data

Same Plex version?

It sounds like a plex issue (windows vs linux). You should report it to them on their forum. We don't touch anything tuner related in the docker image, it's all handled by Plex itself.

When I restart the container, I get that pop up about connecting, but usually connects within 30 seconds or so