You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
They both appear to have the same images. It would be nice if there were versions of your images without the entrypoint; this is what I assume you intended for the non-autobuild? Some tools don't play nicely with entrypoints. Also, most users assume you can run something like docker run -it <image> /bin/bash and entrypoints prevent this.
For a variety of reasons sending a pull request is not possible for me even though this looks like a really easy fix.
I'd like to be able to share your images by directly referencing their dockerhub name, but until a fix for this bug is implemented, the best I can do is suggest people download your docker files, edit them, and rebuild locally.
The text was updated successfully, but these errors were encountered:
The blender-autobuild exists for people who want to pull images that have been built by Docker. The images should otherwise be identical.
I don't understand what the problem is with having the entrypoint defined this way. Can you share an example of tools that have a problem with this? It's designed to be used as a command-line renderer, so it's basically a shortcut to make the container easier to use (<image> <file> instead of <image> blender -b <file>).
You have two repositories on dockerhub
They both appear to have the same images. It would be nice if there were versions of your images without the entrypoint; this is what I assume you intended for the non-autobuild? Some tools don't play nicely with entrypoints. Also, most users assume you can run something like
docker run -it <image> /bin/bash
and entrypoints prevent this.For a variety of reasons sending a pull request is not possible for me even though this looks like a really easy fix.
I'd like to be able to share your images by directly referencing their dockerhub name, but until a fix for this bug is implemented, the best I can do is suggest people download your docker files, edit them, and rebuild locally.
The text was updated successfully, but these errors were encountered: