Environment build fails with "failed to solve: .....: not found"

Issue:  When trying to build an environment which is using a base environment that has failed recent revisions after the actual active one, the build will fail with a message indicating it can not find the image it is using as a base.  

Example:

panic: failed to solve: 172.20.163.146:5000/dominodatalab/environment:637d085f699e846123f35871-6: 172.20.163.146:5000/dominodatalab/environment:637d085f699e846123f35871-6: not found

In this case our build is looking for revision 6 indicated by the -6 at the end of the url for the image: 

> 172.20.163.146:5000/dominodatalab/environment:637d085f699e846123f35871-6

However this revision is marked as failed in our "Environment Base" and the current active and correct revision is actually #4:

Root cause: This behaviour has been identified as a bug in Domino versions 5.x and is set to be fixed in version 5.5.0 

Workaround:  There are a few ways to overcome this problem by either creating a successful build for the "Environment Base" which will set it as the latest active revision or alternatively you could simply copy the "Environment Base" which will create a new environment with no revision history.