I'm bringup
https://hub.docker.com/r/ubuntu/bind9 on hAP ax3. I'll share what I've learned so far.
Mounts have two flavors: (1) file mount, typically configuration file with predefined content, and (2) directory mount, typically empty directory work area to persist content beyond container removal.
Lessons learned so far: (A) file or at least directory must exist before scp or sftp can upload content, (B) DO NOT create empty mount directories before launch, (C) container manager completes mount creaton at launch and appears to define permissions which can't be done in RouterOS which lacks a complete file manager..
The BIND 9 image fails horribly with empty configuration as it tries to write one but doesn't have write permission in parent directory.
The BIND 9 image will start without any mounts and runs with the environment setup alone.
TL;DR setup files with predefined content only; container will do the rest at launch.