[atomic-devel] Announcing CRI-O 1.0.0-rc3

We are happy to announce the release of CRI-O v1.0.0-rc3 . A big thanks to our maintainers and contributors from Red Hat, Intel, SUSE, Hyper, IBM and others. Highlights of the release: 1. Support for limiting

[atomic-devel] Announcing CRI-O 1.0.0-rc2

We are happy to announce the release of CRI-O v1.0.0-rc2 ( https://github.com/kubernetes-incubator/cri-o/releases/tag/v1.0.0-rc2) Big thanks to our maintainers and contributors from Red Hat, Intel, SUSE, Hyper, IBM and others. The main reason behind this second RC is to fix a failure to pull

[atomic-devel] Announcing cri-o 1.0.0-rc1

We are happy to announce the release of CRI-O v1.0.0-rc1 ( https://github.com/kubernetes-incubator/cri-o/releases/tag/v1.0.0-rc1) Big thanks to our maintainers and contributors from Red Hat, Intel, SUSE, Hyper, IBM and others. The first RC brings further stability, performance, and testing to

[atomic-devel] Announcing CRI-O 1.0.0-beta.0

We are happy to announce the release of CRI-O v1.0.0.beta.0 . With this release, we added support for OCI 1.0 specifications. Big thanks to our maintainers and contributors from Red Hat, Intel, SUSE, Hyper, IBM and others.

Re: [atomic-devel] cri-o, buildah and skopeo packages available via Ubuntu PPA and CentOS Virt SIG

cc'ed Nalin On Wed, Jul 5, 2017 at 1:06 PM, Clayton Coleman wrote: > Hrm, maybe when: > >CGroup: /system.slice/crio.service >├─ 8525 /usr/bin/crio --debug >└─12888 storage-untar /var/lib/containers/storage/overlay2/ >

[atomic-devel] Announcing CRI-O 0.3

We are happy to announce the release of CRI-O v0.3 . With this release, we are passing all the k8s node conformance tests. Big thanks to our maintainers and contributors from Red Hat, Intel, SUSE, Hyper, IBM, and others. Highlights

[atomic-devel] Announcing cri-o 0.2

We are happy to announce the release of CRI-O v0.2 . With this release, we have made good progress towards passing the node conformance tests. A big thanks to our maintainers and contributors from Red Hat, Intel, SUSE, Hyper, IBM

[atomic-devel] Announcing cri-o 0.1

We are happy to announce the release of cri-o 0.1. We have been hard at work and a lot of the features are in place. We're able to start a kubernetes cluster and have basic pods up and running. A big thanks to our maintainers and contributors from Red Hat, Intel, SUSE, Hyper, IBM and others.

Re: [atomic-devel] Status of containerizing docker and https://github.com/projectatomic/atomic-system-containers

If we can wait a bit, we should have a new 1.0.0.rc3 for runc soon. On Thu, Mar 16, 2017 at 8:51 AM, Daniel J Walsh wrote: > Mrunal which version of runc should we be shipping? > > > On 03/16/2017 10:01 AM, Giuseppe Scrivano wrote: > > Daniel J Walsh

Re: [atomic-devel] Docker project: Can you have overlay2 speed and density with devicemapper? Yep.

IMO, this doesn't really need any new knobs in the pod spec. This could be handled under the hood in the container runtime level (by config or default). On Wed, Oct 26, 2016 at 11:44 AM, Jeremy Eder wrote: > ​If a user specifies read-only in their podspec...what does that

Re: [atomic-devel] We have a bugzilla requesting that we change the default CMD to systemd for base images in RHEL

On Fri, Oct 21, 2016 at 9:29 AM, Daniel J Walsh wrote: > That might make the most sense. > > RHEL7 == Base Image > > RHEL7Systemd == BaseImage + Config to run systemd as pid1. > +1, maybe call it RHEL7-system image? > > > > On 10/21/2016 12:26 PM, Daniel Riek wrote: > >

Re: [atomic-devel] docker-1.11 handling of runc and containerd.

those docker-* subpkgs though but that would definitely fix this issue > since we'll ship specif versions of those tools *with* docker. However, as > Dan pointed out in the Trello card those binaries should be _hidden_ under > /usr/libexec/docker for instance. > > On Fri, Apr 8, 20

Re: [atomic-devel] docker-1.11 handling of runc and containerd.

I think if allowed, then we should atleast ship a newer version of runc as a separate package. The one that docker needs could be shipped with the docker package as docker-runc. (We could do the same for containerd if we expect usage of it outside of docker.) Thanks, Mrunal On Fri, Apr 8, 2016