I often find conflicts in the environment when using NeMo.
I also had to fix torch to 1.7.1. I also opened a pull request for that, but is not accepted to stick the version of torch. You can read more here https://github.com/NVIDIA/NeMo/issues/1868  and follow until you see my pull request, which is a temporary workaround for me. Maybe you should apply to yourself the same practice. Closing due to inactivity. Please reopen if still having the issue.
I often find/see conflicts in the environment between - torch, torchtext, torchaudio, torchvision, pytorch-lightning and nemo and this causes many problems for me. Also, it seems like many of the issues posted here are related to those conflicts. This is to be expected with the fast pace these libraries are developing, but things could improve for the user when it comes to theses issues. 

A solution would be to post fixed and verified library/environment versions and install readme:s for the environment supporting the release, e.g. an INSTALL.md with fixed versions per release. 

Another solution would be to be more strict with the versions required in the requirements-files under the requirements folder. That would not support anaconda environments, so please also consider to include how to achieve a stable anaconda environment. 

Further more, a nice example is the [pytorch local install page](https://pytorch.org/get-started/locally/), where you could iteratively get instructions how to install.

(OR a novel approach would be to simply tar the environment and offer it as an s3-artefact along with the release, e.g. arm, x86-64 etc?)

Br, PvR