Thanks for your answers. I know that the setup command is run the first one and is the point of failure so the node is not setting up. I have changed the identity path to the one suggested without success and also changed the identity folder to the one the node is going to store the data. That has move forward the error now not binding the path in the identity line of the command instead of the data storage line.
Going against the manual I changed the --mount command for the -v command which allows the command to run but without complaints but it doesn’t create the needed folders and the config.yaml file needed for the storagenode operation so another failure.
I am not a docker expert at all but it sounds to me like docker doesn’t like to bind to lvm volumes? or some extra stuff that I don’t know is needed