2023-08-30, 06:19 PM
Okay, so you don't have a docker group that you added to avoid sudo, which is fine. Not a big deal, more of an annoyance for you.
Your last line might lead you to the answer here -- you generally shouldn't (most times can't) swap between users running the docker container. If you don't specify a user, generally containers don't run as root, they have a user set up inside the container to run as a preset UID/GID that works with the services inside the container. Setting a user/group changes those IDs to match so that file/group permissions work properly with your existing infrastructure. So by giving your user access to the card, then commenting out that information to try and get the card to work, you're muddling things pretty hard.
Looking at your id command output, you don't seem to have access to the video/render group, which means you don't have access to your video card, which could explain why you can't access it in the docker container. Step 4 of the docker guide explicitly states that you should add your user (on the host) to the correct group.
Skipping steps is the primary reason HWA didn't work for me, even if I swore I hit every step previously. Even if you think you don't need something. Note that this last step you're trying to do is just updating dynamic links, per the guide. Follow the guide, step-by-painstaking-step. You need to start, run, and keep the container run by the same user in perpetuity unless you plan to have a full changeover for the foreseeable future. A momentary change can destroy access to your files, databases, etc.. So I'd recommend making the correct steps to ensure your user has the right access. The guide walks you through this.
Your last line might lead you to the answer here -- you generally shouldn't (most times can't) swap between users running the docker container. If you don't specify a user, generally containers don't run as root, they have a user set up inside the container to run as a preset UID/GID that works with the services inside the container. Setting a user/group changes those IDs to match so that file/group permissions work properly with your existing infrastructure. So by giving your user access to the card, then commenting out that information to try and get the card to work, you're muddling things pretty hard.
Looking at your id command output, you don't seem to have access to the video/render group, which means you don't have access to your video card, which could explain why you can't access it in the docker container. Step 4 of the docker guide explicitly states that you should add your user (on the host) to the correct group.
Skipping steps is the primary reason HWA didn't work for me, even if I swore I hit every step previously. Even if you think you don't need something. Note that this last step you're trying to do is just updating dynamic links, per the guide. Follow the guide, step-by-painstaking-step. You need to start, run, and keep the container run by the same user in perpetuity unless you plan to have a full changeover for the foreseeable future. A momentary change can destroy access to your files, databases, etc.. So I'd recommend making the correct steps to ensure your user has the right access. The guide walks you through this.
Jellyfin 10.10.5 LSIO Docker | Ubuntu 24.04 LTS | i7-13700K | Arc A380 6 GB | 64 GB RAM | 79 TB Storage