Goes without saying it sucked to see us still being stuck to the pre-mapped file structure for the docker daemon. We are already asked where we want our apps pool to live, why not allow me to store my data where I want it in a child dataset not the hidden ./ix/_data?
You can - its just that the ix stuff is default
How would this be done correctly with the docker daemon being mapped there already?
Actually I think I misunderstood your question.
Though - where the docker images are doesn’t really matter - it s where you store the data and the config that matters - which can be placed elsewhere
Add binds/mounts for app config/data locations to wherever you want.