Re: [OKD/OCP v4]: deployment on a single node using CodeReady Container
Hi Joel, Yes, CRC requires virtualization. It creates and manages a VM, using the hypervisor provided by your laptop OS, and runs OpenShift inside that VM. AFAIK there is no more all-in-one containerized support for OpenShift so more 'oc cluster up' for OpenShift 4.x. []s, Fernando Lozano On Wed, Sep 18, 2019 at 9:44 AM Joel Pearson wrote: > With CodeReady Container, it's not possible to use it without > virtualisation right? Because it needs CoreOS, and can't startup on an > existing docker installation like you can with "oc cluster up"? > > I'm only asking because I almost got OKD 3.11 running on Windows 10 WSL > (windows subsystem for linux) v2. But if it's a full VM, then running > inside WSL 2 doesn't really make sense (and probably doesn't work anyway). > > On Sat, 14 Sep 2019 at 02:35, Daniel Comnea wrote: > >> Recently folks were asking what is the minishift's alternative for v4 and >> in case you've missed the news see [1] >> >> Hopefully that will also work for OKD v4 once the MVP is out. >> >> >> Dani >> >> [1] >> https://developers.redhat.com/blog/2019/09/05/red-hat-openshift-4-on-your-laptop-introducing-red-hat-codeready-containers/ >> ___ >> users mailing list >> users@lists.openshift.redhat.com >> http://lists.openshift.redhat.com/openshiftmm/listinfo/users >> > > ___ > users mailing list > users@lists.openshift.redhat.com > http://lists.openshift.redhat.com/openshiftmm/listinfo/users > ___ users mailing list users@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/users
Re: [OKD/OCP v4]: deployment on a single node using CodeReady Container
With CodeReady Container, it's not possible to use it without virtualisation right? Because it needs CoreOS, and can't startup on an existing docker installation like you can with "oc cluster up"? I'm only asking because I almost got OKD 3.11 running on Windows 10 WSL (windows subsystem for linux) v2. But if it's a full VM, then running inside WSL 2 doesn't really make sense (and probably doesn't work anyway). On Sat, 14 Sep 2019 at 02:35, Daniel Comnea wrote: > Recently folks were asking what is the minishift's alternative for v4 and > in case you've missed the news see [1] > > Hopefully that will also work for OKD v4 once the MVP is out. > > > Dani > > [1] > https://developers.redhat.com/blog/2019/09/05/red-hat-openshift-4-on-your-laptop-introducing-red-hat-codeready-containers/ > ___ > users mailing list > users@lists.openshift.redhat.com > http://lists.openshift.redhat.com/openshiftmm/listinfo/users > ___ users mailing list users@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/users
RHCOS image for openstack
Hi, I'm trying dev-preview of RHOCP on OpenStack by following https://github.com/openshift/installer/blob/master/docs/user/openstack/README.md The issue I'm facing is that I cannot boot up RHCOS machines. It looks like VM doesn't recognize the RHCOS qcow2 image as bootable disk. I downloaded that image from the following URL indicated by the above document. https://mirror.openshift.com/pub/openshift-v4/dependencies/rhcos/pre-release/latest/ I checked that image. It shows that it is raw file not qcow2. [root@rdo-aio ~]# qemu-img info rhcos-42.80.20190828.2-openstack.qcow2 image: rhcos-42.80.20190828.2-openstack.qcow2 file format: raw virtual size: 656M (687595008 bytes) disk size: 656M [root@rdo-aio ~]# sha256sum rhcos-42.80.20190828.2-openstack.qcow2 c31a1039366ff7f3fa43a0110d28f4c9b36a831d55ea120eb1a4128d1a1905bb rhcos-42.80.20190828.2-openstack.qcow2 # This is correct hash compared to https://mirror.openshift.com/pub/openshift-v4/dependencies/rhcos/pre-release/latest/sha256sum.txt So I suspect there is an issue with the qcow2 image from the URL. Did anyone succeed to create cluster with this image ? Koki Sanagi ___ users mailing list users@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/users
