runtime
runtime copied to clipboard
OCI (Open Containers Initiative) compatible runtime using Virtual Machines
If you pass a stdin to docker run, the container hangs $ echo hello | docker run -i busybox sh: hello: not found .... but the container do not gets...
We should provide an alternate `configuration_kata.toml.in` file in order to generate `configuration_kata.toml`. This would prevent from confusion if we want to test Kata and Clear on the same machine.
Every reference to Clear Containers should be configured depending on the configuration used. In case we test Kata, we want the logger name to be `kata-runtime` instead of `cc-runtime`. Same...
# Description of problem In my host(VM), docker+cc works well, I can create container noemally. But my host network is broken, when I create a pod. Execute command like: ```bash...
# Description of problem When I try to start a container with a (very) long docker run command the runtime errors with something like "message too long" The *real issue*...
The `list` command currently always shows the UID of the owner of the rootfs provided for the container. However, `runc` shows the user **name** by default. If it is unable...
Currently, if `list` is unable to display the UID of the rootfs, it will error. However, we should probably be more tolerant and display a `?` to denote the inability...
Image 20120 added new agent version The agent changed from 4d844b2 to d9790 https://download.clearlinux.org/releases/20120/clear/RELEASENOTES Here is the list of changes merged: ad7c8a5 privileges: Add NoNewPrivileges in the api 4c2b752 devices:...
Now that Docker have finally released the following: - https://download.docker.com/linux/fedora/27/x86_64/stable/Packages/docker-ce-17.12.0.ce-1.fc27.x86_64.rpm ... we need to update and re-test the installation doc for Fedora 27: - https://github.com/clearcontainers/runtime/blob/master/docs/fedora-installation-guide.md
It is not possible to retrieve the hostname of a swarm replica using cc-runtime 3.0.4 with docker 17.06-ce as it leaves the replicas in "create" state. $docker swarm init Swarm...