similar to: C 7, docker, and storage

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

The CentOS Atomic SIG has released an updated version (https://wiki.centos.org/SpecialInterestGroup/Atomic/Download) of CentOS Atomic Host (7.1708), 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. This release, which is based on the RHEL 7.4 source code

Hi everyone, I've been running some tests on Travis CI with CentOS 7 and CentOS 8 based Docker containers and having issues with the CentOS 8 ones. With the centos:8 image, the RPM database eventually gets corrupted due to the default overlay2 storage driver used by Docker. This issue doesn't show with the centos:7 container. It already comes with the "fastestmirror" and

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

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

Anyone? > -------- Original Message -------- > Subject: Persistent storage for docker containers from a Gluster volume > Local Time: June 25, 2017 6:38 PM > UTC Time: June 25, 2017 4:38 PM > From: mabi at protonmail.ch > To: Gluster Users <gluster-users at gluster.org> > Hello, > I have a two node replica 3.8 GlusterFS cluster and am trying to find out the best way

On Mon, Apr 03, 2017 at 05:52:33PM +0000, Spike wrote: > Dear all, > > I'm moving my first baby steps with libvirt-lxc trying to convert over from > an LXD installation and one of the hurdles is putting together an image. > > All the examples I found about libvirt-lxc refer to running /bin/sh in a > container, almost as if it was docker, as opposed to run a "full

Hi All. I am currently running docker 1.13 on Centos 7 boxes with devicemapper storage plugin. I would like to know what are your experiences in regard to: - storage plugins - kernel versions - stability I consider upgrade to docker 17.03.1 and would like to choose most stable combination of kernel/storage plugin. Thanks for all info! BR, Rafal.

Hello, I have a two node replica 3.8 GlusterFS cluster and am trying to find out the best way to use a GlusterFS volume as persistent storage for docker containers to store their data (e.g. web assets). I was thinking that the simplest method would be to mount my GlusterFS volume for that purpose on all docker nodes using FUSE and then simply start containers which require persistent storage with

Hello, i want to use docker with ipv6. i install docker and edit the /etc/docker/daemon.json: { "ipv6": true } Message: [root at froodo network-scripts]# systemctl status docker ? docker.service - Docker Application Container Engine Loaded: loaded (/usr/lib/systemd/system/docker.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Do

Hi, glusterFS is working fine for large files (in most of the cases it's used for VM image store), with docker you'll generate bunch of small size files and if you want to have a good performance may be look in [1] and [2]. Also two node replica is a bit dangerous in case of high load with small files there is a good risk of split brain situation, therefore think about arbiter

On 28-Jun-2017 5:49 PM, "mabi" <mabi at protonmail.ch> wrote: Anyone? -------- Original Message -------- Subject: Persistent storage for docker containers from a Gluster volume Local Time: June 25, 2017 6:38 PM UTC Time: June 25, 2017 4:38 PM From: mabi at protonmail.ch To: Gluster Users <gluster-users at gluster.org> Hello, I have a two node replica 3.8 GlusterFS

ok, thank you Daniel, that helps, I'll see if I can adapt it to other OS and figure out the docker style stuff, it would be useful to run a few things I have in mind. Btw, Daniel, have you ever tried to run libvirt inside a container? I was trying to do so to test things since I didn't want to get all the stuff installed on the host, but I got a whole bunch of errors and virt-manager

On Tue, Mar 12, 2019 at 11:10:40PM +0100, Lars Lindstrom wrote: >Hi everyone! > >I have the following requirement: I need to connect a set of Docker >containers to a KVM. The containers shall be isolated in a way that they >cannot communicate to each other without going through the KVM, which >will act as router/firewall. For this, I thought about the following >simple setup

Hi everyone! I have the following requirement: I need to connect a set of Docker containers to a KVM. The containers shall be isolated in a way that they cannot communicate to each other without going through the KVM, which will act as router/firewall. For this, I thought about the following simple setup (as opposed to a more complex one involving a bridge with vlan_filtering and a seperate VLAN

On 03/03/16 16:23, Lokesh Mandvekar wrote: > > I have rpm sources for centos-release-docker at > https://github.com/CentOS-virt7/centos-release-docker > > Some updated packages available on centos-docker-common-testing branch are: > docker: http://cbs.centos.org/koji/buildinfo?buildID=9932 > atomic: http://cbs.centos.org/koji/buildinfo?buildID=10046 >

I have rpm sources for centos-release-docker at https://github.com/CentOS-virt7/centos-release-docker Some updated packages available on centos-docker-common-testing branch are: docker: http://cbs.centos.org/koji/buildinfo?buildID=9932 atomic: http://cbs.centos.org/koji/buildinfo?buildID=10046 docker-distribution: http://cbs.centos.org/koji/buildinfo?buildID=9950 I think I need to have the

Moving this discussion to centos-virt@ as it's upto the SIG to decide on how this moves ahead. I'm hoping to have 2 new koji tag sets: virt7-docker-fedora-* (will have fedora rpms rebuilt) virt7-docker-el-* (will have rhel candidate builds before they are released or land in centos extras) The -el-* repos will help to have Virt SIG as sort of an upstream and early QA for both RHEL and

On Fri, Jun 10, 2016 at 9:11 PM, Lokesh Mandvekar <lsm5 at fedoraproject.org> wrote: > Moving this discussion to centos-virt@ as it's upto the SIG to decide on > how this moves ahead. > > I'm hoping to have 2 new koji tag sets: > > virt7-docker-fedora-* (will have fedora rpms rebuilt) > virt7-docker-el-* (will have rhel candidate builds before they are released

On Mon, Jun 13, 2016 at 12:23 PM, Nico Kadel-Garcia <nkadel at gmail.com> wrote: > On Mon, Jun 13, 2016 at 6:39 AM, George Dunlap <dunlapg at umich.edu> wrote: >> On Fri, Jun 10, 2016 at 9:11 PM, Lokesh Mandvekar >> <lsm5 at fedoraproject.org> wrote: >>> Moving this discussion to centos-virt@ as it's upto the SIG to decide on >>> how this