-
Notifications
You must be signed in to change notification settings - Fork 59
Failed to run container in cor runtime using Hyper-V #666
Comments
May be it helps systemctl status docker-cordocker-cor.service - Docker Application Container Engine Feb 12 08:56:11 docker-icc-host01.amsokol.me dockerd[369]: time="2017-02-12T08:56:11.891314300Z" level=info msg="API listen on /var/run/docker.sock" |
The same error is in release 13350 |
Hi @amsokol
run your tests again and a log file will be create
please attach it |
Dear @devimc, Done: 2017-02-16T15:05:45.773284Z:517:cc-oci-runtime:debug:called as: /usr/bin/cc-oci-runtime create --bundle /var/run/docker/libcontainerd/dfd9317bddbd683ae399f6ed4088ce7a0bb410d3fea4554a43b7b4ea32f37674 --console /dev/pts/1 --pid-file /run/docker/libcontainerd/containerd/dfd9317bddbd683ae399f6ed4088ce7a0bb410d3fea4554a43b7b4ea32f37674/init/pid dfd9317bddbd683ae399f6ed4088ce7a0bb410d3fea4554a43b7b4ea32f37674 |
@amsokol Could you also paste the output of
|
Hi @amsokol - thanks again for reporting this issue. Unfortunately it is not possible to run a Clear Container in a nested hyperv environment, as documented by Microsoft here: |
Dear jodh-intel, I install trial VMware Workstation 12.5. I try Clear Linux and Clear Containers for Fedora 25. Does Clear Containers supports VMware nested virtualization? |
@amsokol This is an issue with MSR virtualization when -cpu host is used. /usr/src/packages/BUILD/target-i386/kvm.c:1777: kvm_put_msrs: Assertion `ret == cpu->kvm_msr_buf->nmsrs' failed /cc @anthonyzxu |
Hi @amsokol - The simplest approach to get going is to install Clear Containers on a Linux host. We have installation instructions for a number of distrubutions here: If you choose Clear Linux on the host, you only need to run 2 commands:
|
I've seen same error in my local host, is there have any solution to this problem?
|
As an update, more info, and fixes, over here for CC3.x: |
Dear All,
I get the error when I try to run container in Clear Linux (both 13260 and 13330 releases).
Clear Linux is deployed from clear-13330(13260)-hyperv.vhdx.gz with enabled nested virtualization in Hyper-V on Windows 10 x64 (with latest updates).
ERROR:
docker pull bash
Using default tag: latest
latest: Pulling from library/bash
0a8490d0dfd3: Pull complete
12503a53c30a: Pull complete
d3fce0ccf57d: Pull complete
Digest: sha256:d7983e735b8a07443c6c4f87c9dc3386dc00ddbcf2930d44ba24aa958c40967c
Status: Downloaded newer image for bash:latest
docker run -it bash
docker: Error response from daemon: containerd: container did not start before the specified timeout.
Here is my environment (for 13330 release):
docker info
Containers: 1
Running: 0
Paused: 0
Stopped: 1
Images: 1
Server Version: 1.12.6
Storage Driver: overlay
Backing Filesystem: extfs
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
Volume: local
Network: bridge overlay null host
Swarm: inactive
Runtimes: cor runc
Default Runtime: cor
Security Options:
Kernel Version: 4.9.7-80.hyperv
Operating System: Clear Linux Software for Intel Architecture
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 3.855 GiB
Name: docker-icc-host01.amsokol.me
ID: DCO5:TE66:CM56:YU3V:OCB6:E3TP:ADY2:QJWE:TUDJ:2GCD:QV3X:7BOB
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Insecure Registries:
127.0.0.0/8
./clear-linux-check-config.sh container
Checking if host is capable of running Clear Linux* OS for Intel® Architecture in a container
SUCCESS: Intel CPU
SUCCESS: 64-bit CPU (lm)
SUCCESS: Streaming SIMD Extensions v4.1 (sse4_1)
SUCCESS: Virtualisation support (vmx)
SUCCESS: Kernel module kvm
SUCCESS: Kernel module kvm_intel
SUCCESS: Nested KVM support
When I use runc instead of cor everything is OK.
Any ideas?
Thanks,
Alex
The text was updated successfully, but these errors were encountered: