Dockerfile
- Make it possible to build a functioning Blender/Crowdrender image from a base image like debian/Ubuntu/Nvidia etc. Optinos are available to choose the versino of Blender to install into the image.
- Removed the 'local' option, this is replaced by passing through the following options as env vars to the
   running container; persistent; token; secret; machine_uuid

Shell scripts
 - Support the new --override-machine-uuid option for crowdrender.
 - Allow the addon to be mounted from a bind mount so that a development
    branch of Crowdrender can be used inside a container.
 - Modified the install_addon script so that its possible ot run crowdrender from a bind mount
   instead of downloading a version from discovery.

Other Chnages
 - Added a dockerignore file
 - Updated the make file to support docker building with other veresions of Blender.
 - Updated readme
 - Updated the github actions file to include options for building images with specified
    versions of blender.
Separately the secrets for the docket name and token have been changed on github to point to the new crowdrender docker hub.

The Blender download URL was specified as a separate input to the github action file. This is changed so that now the URL is constructed from other variables, namely the short and long version string, allowing you to customise the version of Blender used.

I also removed a build arg from the make file as it was overriding the version number with nothing causing a build error.

…drender/cr-docker into fix-machine-uuid-overriding

Removing refs to deprecated Dockerfiles, updating tags as well

Tested on windows, running WSL2, I can render using an RTX GPU in a container. Seems like the container toolkit isn't required.

Supporting the building of multiple Blender versions is now a lot easier.

I used the matrix builds in actions to create a list of blender versions that will be supported.

Some minor changes to the naming of the repository and the tags are in here too.

Only need the filepath to the addon package now, other options have been removed.

Support for using a copy of the addon that is on the host, but not in the container is done by simply omitting the -i flag, and making sure the local copy is bound to the container using docker's bind mounts.

The sript called for both an image name and a tag, its simpler to just accept the image name with the tag included in it.

Removed checking for this tag as well.

Added a variable to hold the path ot the location the addon should be installed when running a dev session. All dev sessions use a copy of the addon hosted on the host, not in the container, hence the use of a bind mount.

The new V0.6.4 and beyond will reequire a change to the commands used to start a server/worker.

Also, the var "use_local_cr" is now false by default and I've made some effort to consolidate and tidy up.

Docker interprets ENV key value such that the value is always a string, no need for explicit quotation marks.

Nvidia seems to have moved drivers into the toolkit, the cuda/driver images are depracated.

Needs testing on a system that has a GPU though.

Reflects changes to the tags, repo name, supported versions of Blender.

Two sections now, one for support of Docker Desktop and one for linux.

Better reflects the intended target system.

matrix vars not available to b used in the command to build the blender url resulted in a useless URL and no blender being downloaded.

this package isn't included in slim, so adding it.

Was using matrix builds incorrectly, resulting in the Blender URL being wrong.

I've now paired up the short and full version names so that the builds use the correct short and full versions when constructing the blender download URL.

Forgot to carry changes from previous commit to the same lines in the docker desktop build.

Wrong name for the image in the build command.