Forum Comments

A guide to setting up a CR Rendering Node with Docker
In Getting started
tim.walls
Sep 14, 2020
Cool, thanks for the feedback! I will make edits in the morning :-). A few responses: Argh, but good of course... Will try and upgrade in due course :). In the meantime, I'm glad I wrote to use the :bl.2.82_cu_10 tag and not :nvidia ;-). Noted. Actually, if anyone followed my instructions from part one they don't need either, so it's a bit belt-and-braces anyway. I'll amend when I update it. Unfortunately, while this is true, the errors that had me tearing my hair out weren't in the container logs (i.e. weren't coming from the startup script.) After stratup, it's pretty much silent, hence having to dig into the container image to find the actual logs in /root/cr/logging. It would be nice if the runtime logs were also output to stdout for container logging. To be honest, I'm just glad someone else has experienced this bug - it was driving me to question my sanity. Uhuh, noted - I'll update the post to explain this as well. Personal habit/policy - anything long-lived on this machine should be managed by Kubernetes (indeed, if I ever get round to a Part 3 it'll be the helm chart I write to do this). Running directly with "docker run" comes under the heading of quick hack (in the nicest sense of the word - I mean that includes most of my CI build jobs), so I like to clean up after as much as possible :-). Good to know - although is there some CR server component in the matchmaking (as it were?) (And if not, then any ideas why I have two zombie instances for the same server in my connection list..?) I should say when I was writing the post, the CR site was down, meaning I was having to go entirely on my notes and couldn't actually double-check anything - so that comment was born out of tangible frustration :-D. I'll update to include that (and remove the -rm accordingly...) Thanks very much - will post an updated version tomorrow, much appreciated.
1
t

tim.walls

More actions