6 ms·
Docker is trying to alleviate this concern by spinning out and trying to foster alternative runtimes, check out containerd and runc: * https://blog.docker.com/
by friism 10y ago
Docker is trying to alleviate this concern by spinning out and trying to foster alternative runtimes, check out containerd and runc:
* https://blog.docker.com/2016/12/introducing-containerd/ https://blog.docker.com/2016/12/introducing-containerd/
* https://runc.io/ https://runc.io/
- thaJeztah 10y ago> I'm aware of runC but don't know if Docker images are realistically portabl (It wasn't clear from your comment if you were aware of this) Since last year (docker 1.11) docker itself no longer is a runtime, and uses runC as the default runtime (https://blog.docker.com/2016/04/docker-engine-1-11-runc/ https://blog.docker.com/2016/04/docker-engine-1-11-runc/) Additional OCI compliant runtimes can be configured on the daemon (https://docs.docker.com/engine/reference/commandline/dockerd/#docker-runtime-execution-options https://docs.docker.com/engine/reference/commandline/dockerd...), and can be selected per container, using the "--runtime" option on "docker run" (https://docs.docker.com/engine/reference/commandline/run/#options https://docs.docker.com/engine/reference/commandline/run/#op...)