MikroTik Solutions

Changes To Container Limitations
Login

Changes To Container Limitations

Next Previous

Changes to "Container Limitations" between 2026-01-30 08:12:07 and 2026-01-30 08:52:23

︙
16
17
18
19
20
21
22
23

24
25
26
27
28
29
30
31
32
33

16
17
18
19
20
21
22

23
24
25

26
27
28
29
30
31
32








-
+


-









*   orchestration
*   rootless mode
*   image building
*   [local image cache](#cache)
*   [Docker Engine API][DEAPI]
*   volume storage manager
*   per-container limit controls:(^It is possible to set per-container limits on maximum RAM usage as of RouterOS 7.20. Prior, it was a global setting, affecting all running containers collectively.)
*   fine-grained per-container limit controls:(^It is possible to set per-container limits on maximum RAM usage as of RouterOS 7.20; prior, it was a global setting, affecting all running containers collectively. RouterOS 7.21 further allows limiting a container to a subset of the available CPU cores, effectively implementing “`docker run --cpuset-cpus`” but not any of the other `--cpu*` flags, which can do things like limiting a container to a _percentage_ of a single core.)
    *   FD count
    *   PID limit
    *   CPU usage
    *   storage IOPS
    *   `/dev/shm` size limit
    *   terminal/logging bps
    *   [capability][caps] restrictions
    *   [seccomp profiles](https://docs.docker.com/engine/security/seccomp/)
    *   [rlimit]
*   [full hardware pass-thru](#hw)
︙