Passing Docker runOptions over to Wave

Thanks for the detailed answer, @Adam_Talbot !

We actually managed now to set an ENV variable at image creation, to write models from the tool into a different folder than $HOME, removing the requirement to mount $HOME when running the container.

My question was also motivated by a recent issue we had with overwriting the ENTRYPOINT using docker.runOptions, which didn’t pass properly to Wave with Fusion in AWSMegatests: AWS Megatests failing due to entrypoint overwrite not being applied to wave

So for the future, I am still not sure exactly which Docker options will pass over to Wave when run with Fusion without issues and which ones might be overwritten. Is the ENTRYPOINT of the container just a special case because Fusion needs to be the entrypoint of the container?