You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Refactor docker swarm test and add support for modified MTU
- RunCVM nodes are launched on a custom network with a custom MTU
- Nodes detect their MTU, then launch dockerd --mtu accordingly
- Nodes create their own docker_gwbridge network with custom MTU
- After swarm init, primary node recreates ingress network
- Refactored test simplifies and standardises in-node docker.sh logic
[](https://www.youtube.com/watch?v=OENaWDlCWKg"Playing around with RunCVM, a docker runtime plugin")
@@ -89,9 +97,7 @@ RunCVM is free and open-source, licensed under the Apache Licence, Version 2.0.
89
97
- Run unusual container workloads, like `dockerd` and `systemd` that will not run in standard container runtimes
90
98
- Maintain a similar experience within a RunCVM VM as within a container: process table, network interfaces, stdio, exit code handling should broadly similar to maximise compatibility
91
99
- Container start/stop/kill semantics respected, where possible providing clean VM shutdown on stop
92
-
- VM console accessible as one would expect using `docker run -it`, `docker start -ai` and `docker attach` (but stderr is not yet separated from stdout)
93
-
- Support for `docker exec`
94
-
- Good support for most other `docker container` subcommands
100
+
- VM console accessible as one would expect using `docker run -it`, `docker start -ai` and `docker attach` (and so on), generally good support for other `docker container` subcommands
95
101
- Efficient container startup, by using virtiofs to serve a container's filesystem directly to a VM (instead of unpacking an image into a backing file)
96
102
- Improved security compared to the standard container runtime, and as much security as possible without compromising the simplicity of the implementation
97
103
- Command-line and image-embedded options for customising the a container's VM specifications, devices, kernel
@@ -178,7 +184,7 @@ In the below summary of RunCVM's current main features and limitations, [+] is u
178
184
-[-] Bind-mounting host sockets or devices, and `--device` is unsupported
179
185
- Networking
180
186
-[+] The default bridge network is supported
181
-
-[+] Custom/user-defined networks specified using `--network` are supported, including Docker DNS resolution of container names
187
+
-[+] Custom/user-defined networks specified using `--network` are supported, including Docker DNS resolution of container names and respect for custom network MTU
182
188
-[+]`--publish` (or `-p`) is supported
183
189
-[+]`--dns`, `--dns-option`, `--dns-search` are supported
0 commit comments