-
-
Notifications
You must be signed in to change notification settings - Fork 194
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Custom Nodes documentation #42
Comments
I've been following this pattern for installing custom nodes and it does work, however I've found this logged when I run the image. Was still fails to load, although it is installed. Do you have any ideas for how to approach a fix for this, Any help would be much appreciated!
|
@billyberkouwer Sounds like an issue with WAS since your other nodes are working. I would reach out to them instead. Maybe try loading an older version of WAS and see if they broke something. |
Thank you! |
@ecornbower that sounds like a super good idea! Thank you very much. Once #30 is done, we hope that custom nodes can also be added with ease. |
@billyberkouwer You're docker container's most likely missing ffmpeg. Docker doesn't have it installed per default and it's not part of the python packages but rather an apt command. Go ahead and install it yourself by altering the apt-get install -y section of the Dockerfile. WAS requires ffmpeg to work otherwise the import will fail during startup. Cheers |
The current documentation recommends forking the entire repo and modifying the
Dockerfile
in order to add custom nodes.It might be better to recommend creating a new
Dockerfile
and use the pre-build image as a base. For example:It's a lot simpler, quicker to build, and easier to update to the latest release.
The text was updated successfully, but these errors were encountered: