search

ikester / blender-docker

Dockerfiles for Blender
MIT License
72 stars 29 forks source link

No apparent difference between autobuild and non-autobuild #2

Open eap opened 7 years ago

eap commented 7 years ago

You have two repositories on dockerhub 1) https://hub.docker.com/r/ikester/blender/ 2) https://hub.docker.com/r/ikester/blender-autobuild/

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.

ikester commented 4 years ago

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>).