MikroTik Solutions

Changes To Container Limitations
Login

Changes To Container Limitations

Changes to "Container Limitations" between 2025-07-02 07:51:06 and 2025-07-02 13:26:21

533
534
535
536
537
538
539

540




541
542
543
544
545
546
547
533
534
535
536
537
538
539
540

541
542
543
544
545
546
547
548
549
550
551







+
-
+
+
+
+








While it _can_ currently pull from an [OCI] image repo, it does so as part of `/container/add`, which is closer to a `docker create` command than to `docker pull`.



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

RouterOS 7.20 added an explicit `name` parameter to `/container/add`, defaulting to the base image name. (e.g. `iperf3:latest`, without the registry or repository names in front.) These are roughly equivalent:
RouterOS doesn’t let you set the name on creation, much less rename it later. The closest you can come to this is to add a custom `comment`, which you can both set at “`add`” time and after creation.

```
$ docker rename $id NEW-NAME
> /container/set 0 name=NEW-NAME


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

This shortcut for [`stop`](#stop) followed by [`start`](#start) doesn’t exist.

It often ends up being more complex than that because the `stop` operation is asynchronous. There are no flags to make it block until the container does stop, nor a way to set a timeout on it, after which it kills the container outright, as you get with the big-boy engines. You are likely to need a polling loop to wait until the running container’s state transitions to “stopped” before calling `/container/start` on it.