## <a id="exec"></a>`exec`

As of RouterOS 7.20, the following commands are roughly equivalent:

    $ docker exec CONTAINER ls -lR /etc
    $ ssh myrouter '/container/shell cmd="ls -lR /etc" 0'

That is to say, they each pass a multi-argument command to the command shell inside the container, if any, which parses the command and executes it within its confines.
That is to say, they each pass a multi-argument command to `/bin/sh` inside the container, if it exists, which then parses the command and executes it within the container’s confines.

Prior, the only method was via `/container/shell`, which of course only works if there is a `/bin/sh` inside the container.
Prior releases lacked the `cmd` parameter, limiting you to an interactive `/container/shell` call.


## <a id="export"></a>`export`/`save`

There is no way to produce a tarball of a running container’s filesystem or to save its state back to an [OCI] image tarball.

The [documented advice][imgtb] for getting such a tarball is to do this on the PC side via `docker` commands, then upload the tarball from the PC to the RouterOS device.