The only workaround I can see is if you map the volume to a temporary location inside the container and use a symlink or mount --bind (which doesn’t make sense in this scenario) inside the container, There is no workaround on docker level itself.
You can either use (named) volumes the way they are, or use binds. Binds allows mapping an arbitrary host path or file into an arbitrary container path or file.
Depending on the use case, using a bind might be an alternative.