similar to: Package security scanner for CentOS docker containers

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

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

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

Hi All. I am currently searching for a decent image/container/registry scanner. I would like to be able to check images for CVE, at the moment I am using rhel/centos/ubuntu/debian based images. I tried on CentOS7: - openscap (oscap-docker): needs atomic for installation, allows scanning of rhel based images only; - atomic: allows scanning of rhel based images only; - clair: usable in theory for

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

Maybe start over with your configuration. Start with default setup, see if everything is running and then start changing the configuration step by step, see when it goes wrong. I saw you have some ldap configs, maybe outside communication fails, acls? sff level? I saw you were using this el7. I am also fan of using 'professional supported' distributions like el7/centos7. But have a

Hi, We are building docker containers on Centos 7 based machines. Sometimes the docker being built cannot install packages because of some kind of network failure. I just found that restarting the docker container fixes the problems and the builds are successful. Does anyone have a clue what the root cause of this might be? Ta, Andrew

On Tue, Dec 27, 2016 at 12:16:04AM +0000, Guillermo Bisheimer wrote: > I've recently built a docker container to easily install and configure tinc > 1.1pre14 in any machine using docker containers. I've created a Github repo > in https://github.com/bys-control/docker-tinc Great! One comment: ifconfig is considered deprecated on Linux. I'm sure the command will stay around,

I've recently built a docker container to easily install and configure tinc 1.1pre14 in any machine using docker containers. I've created a Github repo in https://github.com/bys-control/docker-tinc I'm working in a WEB based admin interface for managing tinc daemons. Right now it's just a JSON API for tinc, but I'm working in developing the front end. Any

> * What are pros and cons of container vs. VMs? Same as any other containerized setup. We've been running our Samba DCs and file servers in nspawn containers (similar to LXC) for a couple of years, no container-specific issues yet. Though I'm not sure if docker is the right tool for the job; samba as a fat daemon running a bazillion subprocesses orchestrated by a persistent database

Hello, I am trying to figure out, whether there are any best practices how to run a Samba AD DC in a container. First of all: why a container? Because obviously containers require less resources and are easier to update than multiple linux systems ? and I want to spend some of the savings into redundancy (multiple DCs, also distributed to serve different locations). Googling around I found

On Sat, Jul 11, 2020 at 11:18 AM Richard W.M. Jones <rjones@redhat.com> wrote: > > KubeVirt is a custom resource (a kind of plugin) for Kubernetes which > adds support for running virtual machines. As part of this they have > the same problems as everyone else of how to import large disk images > into the system for pets, templates, etc. > > As part of the project

Am 03.09.18 um 17:21 schrieb Robert Marcano: > On 09/03/2018 11:05 AM, Stefan G. Weichinger via samba wrote: >> great, thanks! Which docker image do you use as base image? > > Sent to you a copy of this email with an attachment of the Dockerfile > needed to build the container image. There are two Dockerfile there, one > for Fedora (extremely experimental Samba package there,

Hi, I've decided to use these summer holidays to wrap my head around Docker and its quirks. Spent the last couple weeks working through a Udemy tutorial and a thick book about Docker, and I have Docker CE installed on two machines: * my workstation running OpenSUSE Leap 15.1 * a public sandbox server running CentOS 7 I'm currently fiddling with custom networks and container

On 09/03/2018 11:05 AM, Stefan G. Weichinger via samba wrote: > Am 03.09.18 um 15:12 schrieb Robert Marcano via samba: >> On 09/03/2018 04:10 AM, Stefan G. Weichinger via samba wrote: >>> >>> As I am learning docker lately I came to the idea of using a docker >>> container as a "fallback" DC at sites where there is no budget (or >>>

On Sun, Jul 12, 2020 at 11:16:01PM +0300, Nir Soffer wrote: > On Sat, Jul 11, 2020 at 11:18 AM Richard W.M. Jones <rjones@redhat.com> wrote: > > > > KubeVirt is a custom resource (a kind of plugin) for Kubernetes which > > adds support for running virtual machines. As part of this they have > > the same problems as everyone else of how to import large disk images

On Tue, Mar 21, 2023 at 09:05:12AM -0500, Eric Blake wrote: > > $ podman build -f ci/containers/alpine-edge.Dockerfile -t libnbd-alpine-edge You usually shouldn't need this step when reproducing a problem on CI. Instead just use the container that gitlab has published under the project's registry For any job eg https://gitlab.com/nbdkit/libnbd/-/jobs/3973002673 you'll see at

Am 03.09.18 um 15:12 schrieb Robert Marcano via samba: > On 09/03/2018 04:10 AM, Stefan G. Weichinger via samba wrote: >> >> As I am learning docker lately I came to the idea of using a docker >> container as a "fallback" DC at sites where there is no budget (or >> understanding) for a 2nd physical DC. >> >> That 2nd DC *might* run as docker