How to prevent container from starting successfully if mount point doesn't exist?

[exp]

I configured various bind mounts for a container, which are nested. However, they come from a volume that could under some circumstances not be available. So a bind mount may fail. In particular, it can happen that the mount point in the container does not exist. Sadly the container just fails to start.

Is it possible to still make the container start and create a warning instead?

 

[leesteken]

Maybe a hookscript that changes the CT configuration before starting?

EDIT: I feel like the title of the thread is the exact opposite of your question and that the title as it is now is already covered by the default behavior.