Unable to run Clear Conntainers on Ubuntu 16.04 Server #1060
Comments
|
@chavafg @jcvenegas Hi - any thoughts here? I suspect we have seen the non-existent proxy socket before maybe. |
|
oh, and thanks for the pretty comprehensive report @vinay-y :-) |
|
Hi @vinay-y , agree pretty comprehensive report, for what I can see the timeout was caused because the runtime was waiting for the VM started correctly, but seems that never happend and docker called to
Then run a container again and collect again the |
|
Hi. @jcvenegas A clarification: All the logs I have uploaded are for a physical machine. In addition to testing on this machine I tried on qemu-kvm VMs on the same machine. My goal is to run containers on VMs. But current priority is to get it running on physical machine. After enabling cc-proxy debug logs, output of The logs for same command I provided in previous comment are probably wrong as cc-proxy.service was not active then. Only cc-proxy.socket was active. Thanks again. |
|
@vinay-y thank you, seems that we did not get enough information from proxy logs :(. You could you try running the following script in order to detect if your system could a Clear Container: Could you verify if is there any qemu instance running ? Also could you provide cpu and memory information from your host ? |
|
@jcvenegas Thanks for this. Maybe this was the problem. Can you please tell me how to enable unrestricted guest kvm support? |
|
@vinay-y Can you try a quick test on that system to confirm that it may not be able to support Clear Containers. Can you try running the following command as root or under sudo If your platform can actually run the VM, you will end up on the command prompt. If this hangs, then please send us the kernel boot log. |
|
Hi guys, I encountered the same issue in my local ubuntu machine. The error is same: "cc-oci-runtime:critical:failed to read proxy socket fd", no other error reported/ And I tested my machine by above command "bash ./clear-linux-check-config.sh container" as @jcvenegas mentioned, the result is SUCCESS for all items. I also checked the qemu command as @mcastelino posted, it shows nothing, is there have some issues about my machine? Please give us some tips, thanks. |
|
Hi @mcastelino, Thanks. |
|
Hi @jovizhangwei , |
|
Hi @vinay-y , I guess that issue is not same as this one, the error is also not same, we didn't found clear root cause of that issue, but probably caused by multi-version installed and misused. |
|
@vinay-y you should not end up on your system's command prompt. Rather you should have ended up inside the container environment. If you ended up on the system command prompt, it means that the VM did not launch. However I am surprised that you did not see any other output. I think your system (Nehalem) cannot support clear containers as it lacks Unrestricted Guest mode support. |
|
@mcastelino , is there have any simpler way to check the machine lacks Unrestricted Guest mode? I have some issue with @vinay-y , the qemu command didn't print anything. |
|
I ran into the same error on centos7.3, I follow the https://github.com/01org/cc-oci-runtime/blob/master/documentation/Installing-Clear-Containers-on-Centos-7.md to install clear container the error logs are almost the same. and the result of but the result of when I ran command: I got no results just like vinay-y. looking forward to your help |
|
@devimc not yet, I will try it now and give feedback I tried the CC 3.0, and it works as expected. |
Unable to run Clear Containers on Ubuntu 16.04 Server using docker as it gets timed out waiting for container.
As compatibility for Docker 17.06 is not yet supported as given here, I have setup Docker 17.03.2.
I started a docker daemon using this.
sudo dockerd --add-runtime cor=/usr/bin/cc-oci-runtime.sh --default-runtime=cor --storage-driver=vfsOutput of
sudo docker infois as follows.Now, when I do
sudo docker run -ti --runtime=runc hello-world, everything works fine.But, when I do
sudo docker run -ti hello-world, the output after two minutes is the following.The error on the docker daemon is the following.
Output of
journalctl -u cc-proxy.serviceis this.The content of
/run/cc-oci-runtime/cc-oci-runtime.logis the following.I think the issue is with
critical:failed to read proxy socket fd.Tried running on Ubuntu 16.04 Server and Desktop VMs on same machine. Same error in both.
Thanks for the help.
The text was updated successfully, but these errors were encountered: