The RouterOS CLI isn't a Bourne shell, and the container feature's `entrypoint` and `cmd` option parsers treats them as simple strings, without any of the parsing you get for free when typing `docker` commands into a Linux command shell. The net effect of all this is that you’re limited to two-word commands, one in `entrypoint` and the other in `cmd`, as in the above “`sleep 3600`” hack.

But how then do you say something akin to the following under RouterOS?

    docker run -it alpine:latest ls -lR /etc

You might want to do that in debugging to find out what a given `/etc` file is called and exactly where it is in the hierarchy so that you can target it with a `mount=…` override. If you try to pass it all as…
You might want to do that in debugging to find out what a given config file is called and exactly where it is in the hierarchy so that you can target it with a `mount=…` override. If you try to pass it all as…

    /container/add … entrypoint="ls -lR /etc"

…the kernel will complain that there is no command in the container’s `PATH` called “`ls -lR /etc`”.

You may then try to split it as…