MikroTik Solutions

Changes To Container Limitations
Login

Changes To Container Limitations

Changes to "Container Limitations" between 2024-07-26 23:04:19 and 2024-07-26 23:17:21

296
297
298
299
300
301
302
303

304
305
306


307
308
309
310
311
312
313
296
297
298
299
300
301
302

303
304
305
306
307
308
309
310
311
312
313
314
315







-
+



+
+







    /container/config/set username="" password=""


## <a id="pause"></a>`pause`/`unpause`

No such feature in RouterOS; a container is running or not.

If the container has a shell, you could try a command sequence like this to get the same effect:
If the container has a shell, you could try a command sequence like this to get the pause effect:

    > /container/shell 0
    $ pkill -STOP 'name of entrypoint'

If that worked, sending a `CONT` signal will unpause the process.


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

RouterOS exposes all ports defined for a container in the `EXPOSE` directive in the `Dockerfile`. The only ways to instantiate a container with fewer exposed ports is to either rebuild it with a different `EXPOSE` value or to create a derived container with the `FROM` directive and set a new `EXPOSE` value.

(See also the discussion of [`--publish`](#publish) above.)