July 2017 - cc-devel - Ml01.01.Org

Re: [cc-devel] Rshd can't run in clear container

by Li, Horace

Copy Damien and James as Samuel is on Sabbatical. Damien, would we have any comment on below issue? Thanks, Horace From: Zhi Yong Wu [mailto:zhiyong.wu@ucloud.cn] Sent: Wednesday, July 19, 2017 9:59 PM To: Ortiz, Samuel <samuel.ortiz(a)intel.com> Cc: Zhou, Hongxing <hongxing.zhou(a)intel.com>; Li, Horace <horace.li(a)intel.com> Subject: Rshd can't run in clear container HI, Samuel When we use cc3.0, we hit a issue. If you have time, can you help take a look at this issue? thanks. https://github.com/clearcontainers/runtime/issues/342 Regards, Zhi Yong Wu

3 years, 2 months

4
6
0 / 0

Re: [cc-devel] [Clr-dev] Clear containers and kubernetes guide

by Miguel Bernal Marin

Hi Natalia, On Thu, Jul 06, 2017 at 10:58:21PM +0000, Marin Perez, Natalia wrote: > Hi guys, > > I'm currently trying the guide that you posted here: https://github.com/01org/cc-oci-runtime/wiki/Clear-Containers-and-Kuberne... and I'm having this error. > > root@ip-172-31-39-225:~/go/src/github.com/kubernetes-incubator/cri-o# make && make install > go build -o crio \ > -tags "selinux seccomp libdm_no_deferred_remove" \ > github.com/kubernetes-incubator/cri-o/cmd/crio > > # github.com/kubernetes-incubator/cri-o/cmd/crio > /usr/lib/go-1.8/pkg/tool/linux_amd64/link: running gcc failed: fork/exec /usr/bin/gcc: cannot allocate memory > > Makefile:72: recipe for target 'crio' failed > make: *** [crio] Error 2 > > Not sure if it's because I'm using Kubernetes version 1.7 instead of the 1.6 version that is being used in the guide or if it may probably be something else in my server configuration. Could you please provide some guidance on this? > > Thank you ! I'm including our Clear Containers mailing list. > > Best regards, > Natalia Marín > -- Regards, Miguel Bernal Marin Open Source Technology Center https://clearlinux.org Intel Corporation

3 years, 2 months

1
0
0 / 0

Release 2.2.2

by Venegas Munoz, Jose Carlos

# Release 2.2.2 https://github.com/01org/cc-oci-runtime/releases/tag/2.2.2 ## Changes - Release: version 2.2.2 - Artifacts: Remove OBS common artifacsts between 2.x and 3.x - Versions: Update kernel and image versions - Tests: Change nginx image for swarm tests - Install: Extract autoconf-archive install to separate script ## Shortlog 800c813 Release: version 2.2.2 ef8144e Artifacts: Remove OBS common artifacsts between 2.x and 3.x 73e28fe Versions: Update kernel and image versions 3a9e3d7 Tests: Change nginx image for swarm tests 82cfb1f Install: Extract autoconf-archive install to separate script ## Compatibility with Docker Clear Containers 2.2.2 is compatible with Docker v17.05.0-ce ## OCI Runtime Specification Clear Containers 2.2.2 support the OCI Runtime Specification [1.0.0- rc5][ocispec] ## Clear Linux Containers image Clear Containers 2.2.2 requires at least Clear Linux containers image [16180][clearlinuximage] ## Clear Linux Containers Kernel Clear Containers 2.2.2 requires at least Clear Linux Containers kernel 4.9.35-76 # Installation CentoOS: https://github.com/01org/cc-oci-runtime/blob/master/documentat ion/Installing-Clear-Containers-on-Centos-7.md Ubuntu: https://github.com/01org/cc-oci-runtime/blob/master/documentati on/Installing-Clear-Containers-on-Ubuntu.md Fedora: https://github.com/01org/cc-oci-runtime/blob/master/documentati on/Installing-Clear-Containers-on-Fedora.md Clearlinux: https://github.com/01org/cc-oci-runtime/blob/master/documen tation/Installing-Clear-Containers-on-ClearLinux.md # Issues & limitations - Qemu segfault (free(): invalid pointer) running dnf install #669 - DNS Resolution in Swarm #854 - docker rm -f reports 'Driver devicemapper failed to remove root filesystem' #795 [clearlinuximage]: https://download.clearlinux.org/releases/16180/clear /clear-16180-containers.img.xz [ocispec]: https://github.com/opencontainers/runtime-spec/releases/tag/ v1.0.0-rc5

3 years, 2 months

1
0
0 / 0

Issues when compiling cc-oci-runtime/proxy

by Li, Horace

Hi, All, I was about to compile and run metrics-tests by pulling the source base from https://github.com/01org/cc-oci-runtime. When compiling cc-proxy, it was reported that "cannot find package "github.com/containers/virtcontainers/hyperstart"". Looking at the link in the report, it looks like hyperstart directory is not existed under github.com/containers/virtcontainers/ anymore but it was imported in vm.go. Would this be fixed? Thanks, Horace

3 years, 2 months

2
3
0 / 0

2020

2019

2018

2017

2016

cc-devel July 2017