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

This is `/container/add file=oci-image.tar` in RouterOS.


## <a id="info"></a>`info`
## <a id="info" name="inspect"></a>`info`/`inspect`

With the understanding that RouterOS has far fewer configurables than a big-boy container engine, the closest command to this in RouterOS is `/container/config/print`. The output is in typical RouterOS “print” format, not JSON.
With the understanding that RouterOS has far fewer configurables than a big-boy container engine, the closest commands in RouterOS are:


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

The closest approximation to this in RouterOS is 

    /container/print detail where …
* `/container/print detail where …`
* `/container/config/print`

You get only a few lines of information back from this, mainly what you gave it to create the container from the image. You will not get the pages of JSON data the Docker CLI gives.
Their output is in typical RouterOS “print” format, not JSON, and you get only a few lines of information back from each, not the pages of details the Docker CLI gives.

A related limitation is that the configurable items are often global in RouterOS, set for all containers running on the box, not available to be set on a per-container basis. A good example of this is the memory limit, set via `/container/config/set ram-high=…`.
A related limitation is that configurable parameters are often global in RouterOS, set for all containers running on the box, not available to be set on a per-container basis. A good example of this is the memory limit, set via `/container/config/set ram-high=…`.


## <a id="kill" name="stop"></a>`kill`/`stop`

RouterOS doesn’t make a distinction between “kill” and “stop”. The `/container/stop` command behaves more like `docker kill` or `docker stop -t0` in that it doesn’t try to bring the container down gracefully before giving up and killing it.