# Passing Docker runOptions over to Wave

**URL:** <https://community.seqera.io/t/passing-docker-runoptions-over-to-wave/509>\
**Category:** Ask for help\
**Created:** [February 21, 2024, 4:54pm UTC](https://community.seqera.io/t/passing-docker-runoptions-over-to-wave/509 "2024-02-21T16:54:55Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![FloWuenne](https://dub1.discourse-cdn.com/flex013/user_avatar/community.seqera.io/flowuenne/32/325_2.png) [@FloWuenne](https://community.seqera.io/u/FloWuenne)\
**Post date:** [February 22, 2024, 10:15am UTC](https://community.seqera.io/t/passing-docker-runoptions-over-to-wave/509/3 "2024-02-22T10:15:31Z")

</div>

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](https://community.seqera.io/t/aws-megatests-failing-due-to-entrypoint-overwrite-not-being-applied-to-wave/486)

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?

---

_[View the full topic](https://community.seqera.io/t/passing-docker-runoptions-over-to-wave/509)._