Changes to "Container Limitations" between 2024-07-25 05:46:24 and 2024-07-25 05:48:27
︙
51
52
53
54
55
56
57
58
59
60
61
62
63
64
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
+
+
The single biggest area of difference between the likes of Docker and the RouterOS `container.npk` feature is how you create containers from OCI images.
RouterOS combines Docker’s `create` and `load` commands as `/container/add`, the distinction expressed by whether you give it the `remote-image` or `file` option, respectively.
<a id="run"></a>There is no shorthand command like `docker run` for creating and starting a container in a single step. Moreover, the lack of Linux-like interactive terminal handling means a simple command like…
$ docker run --rm -it alpine:latest
sh-5.1# <do something inside the container>
sh-5.1# exit
…is most briefly expressed under RouterOS as…
> /container
> add remote-image=alpine:latest veth=veth1 entrypoint=sleep cmd=3600
… wait for it to download and extract …
… poll with "print" commands to get the container ID …