[BUG] Blender does not start with container #10
Comments
|
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid. |
|
I can only confirm what I can test, I run Debian Bookworm and have tried on it and Fedora 40. Here is a test Run: This is with a 3060 and I have full CUDA support and accelerated preview rendering running the |
|
Interesting, thanks for this. When I run your exact command on my machine, which has very similar hardware(!), I don't have CUDA or OptiX support... 
However, it does (evidently) launch blender, with just one seemingly benign error message shown in the console: In fact, when using I did note that when using I also reproduced this with a minimal services:
blender:
image: linuxserver/blender:latest
restart: unless-stopped
container_name: blender
environment:
- PGID=1003
runtime: nvidia
ports:
- 0.0.0.0:3000:3000/tcp
volumes:
- /media/data/blender-config:/config
- /media/data/blender-cache:/var/cache/blender
# Add all the GPU capabilities
deploy:
resources:
reservations:
devices:
- driver: nvidia
count: all
capabilities: [compute, gpu, graphics, utility, video, display]
# Increase shared memory size
shm_size: '1gb'I've just been playing with a bunch of additional combinations, and have noted the following. These are additive to the
I've then worked backwards:
In summary, I for some reason need to set the group to my host's So, I'm a bit confused about this if I'm honest, especially as you're basically on the same hardware architecture, with the main difference being that you're running Debian instead of Arch... Can I ask you to share your nvidia-container-runtime configuration file? Mine is at The other thing that crosses my mind is cgroups, maybe I should look into that again. #accept-nvidia-visible-devices-as-volume-mounts = false
#accept-nvidia-visible-devices-envvar-when-unprivileged = true
disable-require = false
supported-driver-capabilities = "compat32,compute,display,graphics,ngx,utility,video"
#swarm-resource = "DOCKER_RESOURCE_GPU"
[nvidia-container-cli]
debug = "/var/log/nvidia-container-toolkit.log"
environment = []
#ldcache = "/etc/ld.so.cache"
ldconfig = "@/sbin/ldconfig"
load-kmods = true
#no-cgroups = true
#path = "/usr/bin/nvidia-container-cli"
#root = "/run/nvidia/driver"
user = "root:root"
[nvidia-container-runtime]
#debug = "/var/log/nvidia-container-runtime.log"
log-level = "info"
mode = "auto"
runtimes = ["docker-runc", "runc", "crun"]
[nvidia-container-runtime.modes]
[nvidia-container-runtime.modes.cdi]
annotation-prefixes = ["cdi.k8s.io/"]
default-kind = "nvidia.com/gpu"
spec-dirs = ["/etc/cdi", "/var/run/cdi"]
[nvidia-container-runtime.modes.csv]
mount-spec-path = "/etc/nvidia-container-runtime/host-files-for-container.d"
[nvidia-container-runtime-hook]
path = "nvidia-container-runtime-hook"
skip-mode-detection = false
[nvidia-ctk]
path = "nvidia-ctk" |
|
Sure, one quick thing when you say working keep in mind that yes for rendering it will use CUDA etc, but the actual onscreen preview of the model is rendered in OpenGL which is why we want to automatically inject the Zink override, otherwise all your rotations and previews use LLVMPipe and that is a GPU emulated on your CPU. It is night and day when you get it working. Here is my runtime config: Also I know Arch is more head but I run a backport kernel (6.6.13) and current nvidia runtime: Maybe it is the |
|
Thanks for that 🙂
I've had to go out, so am on my phone now. I did comment out that permissions line, rebooted and got a runtime permissions error... I also tried changing it to root:vglusers, but no joy there either, nor running as sudo.
Can I ask if you set up rootless mode?
The way I run my containers is by adding my user to the docker group, but I never set up rootless mode. I guess I should try that next?
Cheers,
Alex
…________________________________
From: Ryan Kuba ***@***.***>
Sent: Thursday, May 30, 2024 4:53:16 PM
To: linuxserver/docker-blender ***@***.***>
Cc: ALB.Leach ***@***.***>; Author ***@***.***>
Subject: Re: [linuxserver/docker-blender] [BUG] Blender does not start with container (Issue #10)
Sure, one quick thing when you say working keep in mind that yes for rendering it will use CUDA etc, but the actual onscreen preview of the model is rendered in OpenGL which is why we want to automatically inject the Zink override, otherwise all your rotations and previews use LLVMPipe and that is a GPU emulated on your CPU. It is night and day when you get it working.
Here is my runtime config:
#accept-nvidia-visible-devices-as-volume-mounts = false
#accept-nvidia-visible-devices-envvar-when-unprivileged = true
disable-require = false
supported-driver-capabilities = "compat32,compute,display,graphics,ngx,utility,video"
#swarm-resource = "DOCKER_RESOURCE_GPU"
[nvidia-container-cli]
#debug = "/var/log/nvidia-container-toolkit.log"
environment = []
#ldcache = "/etc/ld.so.cache"
ldconfig = "@/sbin/ldconfig"
load-kmods = true
#no-cgroups = false
#path = "/usr/bin/nvidia-container-cli"
#root = "/run/nvidia/driver"
#user = "root:video"
[nvidia-container-runtime]
#debug = "/var/log/nvidia-container-runtime.log"
log-level = "info"
mode = "auto"
runtimes = ["docker-runc", "runc", "crun"]
[nvidia-container-runtime.modes]
[nvidia-container-runtime.modes.cdi]
annotation-prefixes = ["cdi.k8s.io/"]
default-kind = "nvidia.com/gpu"
spec-dirs = ["/etc/cdi", "/var/run/cdi"]
[nvidia-container-runtime.modes.csv]
mount-spec-path = "/etc/nvidia-container-runtime/host-files-for-container.d"
[nvidia-container-runtime-hook]
path = "nvidia-container-runtime-hook"
skip-mode-detection = false
[nvidia-ctk]
path = "nvidia-ctk"
—
Reply to this email directly, view it on GitHub<#10 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAC3ZLNNJELOSIY5FZQVRVLZE5DOZAVCNFSM6AAAAABIQKSJ7KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNBQGAZTGMRZGM>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
|
No we use S6v3 init and require root for all out images. Everything runs in userspace as the abc user in the container, but we have hooks that run on init that require root in the container like chowning the video device. |
|
Does this work? (given your error) |
|
Hi, yeah I've already got those nvidia_drm kernel mode options set actually, which I got from the arch wiki, at https://wiki.archlinux.org/title/NVIDIA#DRM_kernel_mode_setting
I had a brief look at S6 a couple of days ago. So you run your containers as root then?
…________________________________
From: Ryan Kuba ***@***.***>
Sent: Thursday, May 30, 2024 8:12:15 PM
To: linuxserver/docker-blender ***@***.***>
Cc: ALB.Leach ***@***.***>; Author ***@***.***>
Subject: Re: [linuxserver/docker-blender] [BUG] Blender does not start with container (Issue #10)
Does this work? (given your error)
slint-ui/slint#4828 (comment)<slint-ui/slint#4828 (comment)>
—
Reply to this email directly, view it on GitHub<#10 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAC3ZLJCXCH2MORSRYXZ7I3ZE52Y7AVCNFSM6AAAAABIQKSJ7KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNBQG4YTCOJVGI>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
|
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions. |
Is there an existing issue for this?
Current Behavior
I just updated the container image to the latest tag (currently 4.1.1), and blender does not launch. It appears to be something to do with X trying to use MESA and zink?
When accessing the web server, KasmVNC loads fine, but I just get a black screen. Running
psin the container shows thatblenderis not launched. However, if I launch blender manually within the container, then it shows up in my web browser.Expected Behavior
Blender should start with the container.
Steps To Reproduce
I have an NVIDIA GPU and am running with
docker compose, using the nvidia-container-runtime. I also extend the base image by installingnvidia-cuda-toolkit. This has worked fine for several months, allowing me to render on my RTX 3070 graphics card.However, since updating to the latest image, version 4.1.1, bringing up the container won't bring up blender...
I found that I can fix the behaviour by first installing
python3-xdgand then editing/defaults/startwm.shand commenting out the environment variables which are being set. I then searched for what commit and what repository added these environment variables tostartwm.sh...So, it was in the
docker-baseimage-kasmvncrepository where these environment variables were added... However, on the same day that a commit added these environment variables (linuxserver/docker-baseimage-kasmvnc@421ff46), they were removed in a later commit (linuxserver/docker-baseimage-kasmvnc@c8a520d).So, perhaps the bug should be reported there, but the thing is, they've already fixed it... Just maybe not in a release? I've not quite figured that part out, but either way, please can you update your latest release to include that commit?
Environment
CPU architecture
x86-64
Docker creation
Container logs
The text was updated successfully, but these errors were encountered: