similar to: New CentOS Atomic Host with OverlayFS Storage

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When

Last week, the CentOS Atomic SIG released an updated version (https://wiki.centos.org/SpecialInterestGroup/Atomic/Download) of CentOS Atomic Host (7.1707), a lean operating system designed to run Docker containers, built from standard CentOS 7 RPMs, and tracking the component versions included in Red Hat Enterprise Linux Atomic Host. The release, which came as part of the monthly CentOS release

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When

Hi, currently, libguestfs does not support the inspection of OSTree/Atomic disk images [1]. While this means that certain tools which use inspection to automatically mount all the partitions available (virt-customize, virt-builder, virt-sysprep, virt-diff, guestfish -i, and the default modes of virt-cat, virt-log, virt-edit) will fail, although it's still possible to manually mount partitions

Gianluca Cecchi <gianluca.cecchi at gmail.com> wrote: > Date: Thu, 30 Nov 2017 09:55:58 +0100 > On Wed, Nov 29, 2017 at 10:23 PM, <m.roth at 5-cent.us> wrote: > >> The latter would explain the message my user's job gave him when it tried >> to umount / >> >> A bit of googling, and I see something called overlayFS can be used... but >> I know

An updated version of CentOS Atomic Host (tree version 7.1706), is now available. [1] CentOS Atomic Host is a lean operating system designed to run Docker containers, built from standard CentOS 7 RPMs, and tracking the component versions included in Red Hat Enterprise Linux Atomic Host. [1] https://wiki.centos.org/SpecialInterestGroup/Atomic/Download CentOS Atomic Host is available as a

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When

Was working on docker on a server, and on startup, I see Nov 29 10:58:27 <servername> dockerd-current: time="2017-11-29T10:58:27.612849959-05:00" level=warning msg="devmapper: Usage of loopback devices is strongly discouraged for production use. Please use `--storage-opt dm.thinpooldev` or use `man docker` to refer to dm.thinpooldev section." Nov 29 10:58:27

Thanks Ady, tried current master and shortened path to /boot/vmlinuz. Same stuff. OSTree doesn't really come into play at this stage, it is just booting the kernel. So I would rather suspect that there is something between ext4, extlinux and qemu. On 03/21/2017 04:01 AM, Ady Ady via Syslinux wrote: >> Hi, >> >> I'm trying to make Syslinux, OSTree and Qemu work

Hi, I'm trying to make Syslinux, OSTree and Qemu work together. So I've made an image, installed Syslinux v. 6.0.3 on it with extlinux and try to boot it. Unfortunately it stops on the stage of loading the kernel with Loading /boot/ostree/agl-17980142f6d5ef5e82153aa533ffb9775181f93248e62a4821f925cdf1b81c34/vmlinuz... failed: I/O error The vmlinuz file is just a normal bzImage (v.

> Clarification for below logs: > > - 'dev_static' is the gluster volume. > - 'int-kube-01' is the gluster client. > - '10.51.70.151' is the first node in a three node (2 replica, 1 arbiter) gluster cluster. > - '/var/lib/kubelet/...../iss3dev-static' is a directory on the client that should be mounting

Hi, I have the following setup in place: 1 node : RancherOS having Rancher application for Kubernetes setup 2 nodes : RancherOS having Rancher agent 1 node : CentOS 7 workstation having kubectl installed and folder cloned/downloaded from https://github.com/gluster/gluster-kubernetes using which i run Heketi setup (gk-deploy -g) I also have rancher-glusterfs-server container running with

> Hi, > > I'm trying to make Syslinux, OSTree and Qemu work together. So I've made > an image, installed Syslinux v. 6.0.3 on it with extlinux and try to > boot it. Unfortunately it stops on the stage of loading the kernel with > > Loading > /boot/ostree/agl-17980142f6d5ef5e82153aa533ffb9775181f93248e62a4821f925cdf1b81c34/vmlinuz... > failed: I/O error >

The team behind the "Samba in Kubernetes" project is happy to announce our second batch of releases. Release v0.3 includes both features and fixes across our set of five release-ready repositories. These are the samba-operator, samba-container, smbmetrics, svcwatch, and sambacc projects. Our little organization may be called "Samba in Kubernetes" but the projects go beyond

On Tuesday 27 May 2014 14:25:08 Richard W.M. Jones wrote: > So I think an API which looks like this ... > > required params: > > None > > optional params: > > path => > Either a directory to be relabelled recursively, or a single > file (defaults to "/"). > > root => > Inspection root of guest. Optional, only

Adding more people to the thread. I am currently not able to analyze the logs. On Thu, Jul 27, 2017 at 5:58 AM, Bishoy Mikhael <b.s.mikhael at gmail.com> wrote: > Hi Talur, > > I've successfully got Gluster deployed as a DaemonSet using k8s spec file > glusterfs-daemonset.json from > https://github.com/heketi/heketi/tree/master/extras/kubernetes > > but then when I

> On 8 Nov 2017, at 9:03 pm, Nithya Balachandran <nbalacha at redhat.com> wrote: > > > That is not the log for the mount. Please check /var/log/glusterfs/var-lib-mountedgluster.log on the system on which you are running the mount process. > > Please provide the volume config details as well (gluster volume info) from one of the server nodes. > Oh I'm sorry, I

Hi Bishoy, Adding Talur who can help address your queries on Heketi. @wattsteve's github repo on glusterfs-kubernetes is a bit dated. You can either refer to gluster/gluster-kubernetes or heketi/heketi for current documentation and operational procedures. Regards, Vijay On Fri, Jul 21, 2017 at 2:19 AM, Bishoy Mikhael <b.s.mikhael at gmail.com> wrote: > Hi, > > I'm

Hi Talur, I've successfully got Gluster deployed as a DaemonSet using k8s spec file glusterfs-daemonset.json from https://github.com/heketi/heketi/tree/master/extras/kubernetes but then when I try deploying heketi using heketi-deployment.json spec file, I end up with a CrashLoopBackOff pod. # kubectl get pods NAME READY STATUS RESTARTS AGE