thank you @James Crowther for the ping, I could reproduce the issue and I have pushed an update, which adds "machine_uuid" as an optional parameter by default it will get set using a random UUID @Wolvenmoon Z can you try if the issue is fixed for you now? Pls also keep in mind, that you have to set the port range to something different than 9000-9025 for the second container, otherwise you will get a socket bind error. you can do that by removing the "--net=host" parameter and e.g. add: -p 9100-9125:9000-9025/tcp

@tim.walls 1. true this is actually good advice to use a stable tag, hence I offer them 2. -- 3. I fully agree, I actually requested this feature multiple times to @James Crowther , do you have any updates on that? ;) It would be awesome to have errors in STDOUT when passing a certain CLI argument 4. -- 5. You might link to the documentation: https://docs.blender.org/manual/en/dev/render/eevee/limitations.html#headless-rendering under "Headless Rendering" section at the bottom I am still trying to find a workable solution, this is a huge problem for my own renderfarm as well 6. fair enough, was just curious 7. AFAIK there were additional features planned, when you connect the client with your account, but as of now I am not aware of any, but I could be wrong, maybe @James Crowther can answer that question better. Also I personally have to add, that I would like to be able to render completely offline too, so hopefully we can do that once the client gets open sourced. I thank you for the good writeup, since now I can point ppl to it, when they are searching for a complete setup guide. 👌

this is a great read @tim.walls , here are a few of my thoughts: 1. first I apologize for the very bad timing, but I just updated all my images to Blender 2.83 LTS after I finally could fix the stupid "GPU does not get used for some unknown reason" bug 2. the switch --runtime nvidia is deprecated and - while it still works - should not be used anymore. The replacement is --gpus all 3. if you want to see the logs of the start script, you can use docker logs -f the name of container is what got specified with --name 4. the missing audio device bug is very weird. To me this happened only on Ubuntu based systems, on my Debian 10 render server that doesn't happen. It is weird, because when using -noaudio it should get ignored.... 5. Eeevee does produce black images, because Blender does not support Eeevee on headless systems. They need an Xserver and an attached display for some OpenGL stuff, all workarounds I have tried so far produced completely broken images (not black ones though...) Blender devs said, that they are working on a solution, albeit with a low priority. 6. why do you pass --rm to the run command? Normally there shouldn't be a reason to create a new container on each start 7. the start script does download the addon on the first start, but once downloaded it does reuse it. So you only connect to the CR server once. Sadly as long as the CR addon is not openSource, there is no other way for me to do that.... :(

I am really sorry for this late reply @drager88.st , but sadly the CR forum was broken for me and I couldn't load any page nor answer whatsoever. You replace "" with the token you get from the CR profile page and you invoke it without the < or >. as described in my README file on GitHub --name does only give the docker image a name, you can call it whatever you want. --net=host does set the docker container into the same network as your host, this way the CR addon is allowed to open the ports it needs automatically. As an alternative, you could port forward the ports 9000 - 9025 manually from the host to the container Again as I said, in the README on the GitHub page, I have described how to set the proper settings in order to get the Blender and CR version you want. The Blender version does matter and right now 2.79b, 2.82a and 2.83 LTS are supported. You upgrade the docker container by deleting it and creating a new one with the Blender and CR version you want. @tim.walls has created an guide explaining a bit more in detail: https://snowgoons.ro/posts/2020-09-11-setting-up-a-blender-rendering-node-part-2/ In case you have still trouble, you can also write me a PM via Discord: zocker_160#5285

if you have docker installed, you are only one command away :), the instructions on the GitHub page should be clear. Here an example setup, then it maybe is more clear: $ docker run -t \ --name "Crowdrender-Server" \ --net=host \ -e token= \ -e CR_VERSION=cr_023_bl279 \ zocker160/blender-crowdrender:bl_2.79 the `\` is only to make it more readable, you can also put everything into one line (without the `\`.

got notification via mail

for everybody interested, I just want to give a quick update: all my docker images moved into an official docker repo, which is public and can be found here: https://github.com/crowdrender/cr-docker the commands are the same, as I still maintain those images ;) on Docker Hub I merged the CPU and GPU repos into one single one: https://hub.docker.com/r/zocker160/blender-crowdrender feel free to create an issue on GitHub or ask questions if you have any!

Hi, it depends on how you want to use your render node. For a system with a GUI and a DE, I recommend using a (small) Ubuntu LTS based distro like Linux Mint XFCE If you want to have a headless render server, I recommend Debian 10 with Docker on top, this way you minimize the overhead of the system itself. If you need help in setting it up, feel free to ask me. ;)

@juliangrendell new images are out running with CR 0.1.7 and Blender 2.79 / 2.80 https://cloud.docker.com/u/zocker160/repository/docker/zocker160/blender-crowdrender https://cloud.docker.com/u/zocker160/repository/docker/zocker160/blender-crowdrender-nvidia

@Benjamin Smith the CLI command has changed with CR 0.1.7 a bit, I've updated the gist on my Github: https://gist.github.com/zocker-160/0688a4902421158b66f52dff3966058a I've updated the Docker images to CR 0.1.7 for Blender 2.79 and 2.80 as well: https://cloud.docker.com/u/zocker160/repository/docker/zocker160/blender-crowdrender

@juliangrendell Docker images for Blender 2.8 are now available in the docker repo you need to use the tag "bl_2.80" I did test it with the latest blender 2.80.45

@juliangrendell Container for 2.8 will come very soon! And yes you are right, the GitHub Repo is not public (yet? @James Crowther), that's why you get a 404 error.

@juliangrendell the docker images are available on the docker hub for some time now;) just search for "crowdrender" or use this link: https://hub.docker.com/r/zocker160/blender-crowdrender would love to get some feedback and feel free to contact me, if you have any questions or problems EDIT: Blender 2.8 images are in the works, so keep an eye on the repo for updates ;)

@James I just did that ;)

@James Hi, I have 3 working Docker images based on blender 2.79b: • CPU only • including nvidia drivers (cuda 9.2) • including nvidia drivers (cuda 7.5) for older GPUs am I allowed to publish them on hub.docker.com ? if yes: under what license can I publish them? if no: how can I share it with you then? PS: I'll make images based on blender 2.8 and cuda 10 as well

Hi everyone, I have completely forgotten about this forum, but my headless server with CR 0.1.6 works with no problems on GPU and CPU. I have created a small HowTo guide here: https://gist.github.com/zocker-160/0688a4902421158b66f52dff3966058a I would like to create a Docker image for that as well, so it can be easily set up, but I don't know if I am allowed to bundle the addon, since you have to sign up in order to download it. Maybe we can find a solution for that ;)

Hello everyone, I'm trying to setup a headless debian server as a renderclient for CR, but I ran into this problem: > ./blender -noaudio -b -P 2.79/scripts/addons/crowdrender/src/bl_2_79/serv_int_start.py -- -t "server_int_proc" Read prefs: /Programme/Blender/2.79/config/userpref.blend found bundled python: /Programme/Blender/2.79/python Exception in module register(): '/Programme/Blender/2.79/scripts/addons/object_boolean_tools.py' Traceback (most recent call last): File "/Programme/Blender/2.79/scripts/modules/addon_utils.py", line 350, in enable mod.register() File "/Programme/Blender/2.79/scripts/addons/object_boolean_tools.py", line 1451, in register km = wm.keyconfigs.addon.keymaps.new(name='Object Mode') AttributeError: 'NoneType' object has no attribute 'keymaps' Exception in module register(): '/Programme/Blender/2.79/scripts/addons/crowdrender/__init__.py' Traceback (most recent call last): File "/Programme/Blender/2.79/scripts/modules/addon_utils.py", line 350, in enable mod.register() File "/Programme/Blender/2.79/scripts/addons/crowdrender/__init__.py", line 101, in register select_platform() File "/Programme/Blender/2.79/scripts/addons/crowdrender/__init__.py", line 71, in select_platform set_sys_path('Linux') File "/Programme/Blender/2.79/scripts/addons/crowdrender/__init__.py", line 92, in set_sys_path addons_path = bpy.utils.script_paths(subdir="addons")[1] IndexError: list index out of range Traceback (most recent call last): File "/Programme/Blender/2.79/scripts/addons/crowdrender/src/bl_2_79/serv_int_start.py", line 17, in crowdrender = sys.modules[cr_pkg] KeyError: 'crowdrender' Blender quit it's the latest version of the addon Thanks in advance!