Update blender version on sample Dockerfile

[n-jay]

Link the Issue(s) this Pull Request is related to.
PR related email thread linked here.

Summarize your change.
Updates the Blender version in sample Dockerfile to latest LTS release: v3.3

This change was made to complement the upcoming OpenCue Blender addon. Related discussion: #312

[n-jay]

@bcipriano something I noticed and wanted to clarify before merging.
Should /usr/local/blender be set as the WORKDIR?

[bcipriano]

@n-jay It's kind of a matter of preference. I don't think it's strictly necessary here, but you could use it if you want.

If there are a lot of other Dockerfile instructions that need to run within that directory, it does help keep the Dockerfile simple. On the other hand, in a standard build-and-install process, if you set your WORKDIR to the install directory, you can end up with some unneeded build artifacts in the install directory, which can make things messy for future users.

An alternative in this case could be to use ARG to set the path as a variable:

ARG BLENDER_INSTALL_DIR=/usr/local/blender
...
RUN mkdir "${BLENDER_INSTALL_DIR}"
<and so on>

This would reduce repetition, make it easy to change the directory in the future (you only have to update one line instead of several), and lets users override it with a custom value at build time via --build-arg.

https://docs.docker.com/engine/reference/builder/#arg

[n-jay]

If there are a lot of other Dockerfile instructions that need to run within that directory, it does help keep the Dockerfile simple. On the other hand, in a standard build-and-install process, if you set your WORKDIR to the install directory, you can end up with some unneeded build artifacts in the install directory, which can make things messy for future users.

Noted,
I went ahead with the ARG alternative you suggested, thanks for that!

[bcipriano]

Thanks! LGTM