similar to: Notes on building libguestfs in a systemd-nspawn container

On Thu, Jan 30, 2014 at 11:50:35AM +0530, Kashyap Chamarthy wrote: > > - Single `make` job timing to compile everything: > > > > real 31m9.792s > > user 17m18.359s > > sys 13m17.868s > > For comparison, on the _host_, the same single `make` job timing: > > real 13m41.440s > user 13m5.816s > sys 1m9.911s

On 01/30/2014 07:41 AM, Kashyap Chamarthy wrote: > Last night I was tinkering with `systemd-nspawn` -- namespace based > container for testing, I thought I'll post what I tried with libguestfs > here: > > > Prerequisite > ------------ > > Because of an audit subsystem incompatibility bug - rhbz#966807[1], turn > off auditing by booting the host w/

On 01/30/2014 03:58 PM, Richard W.M. Jones wrote: > On Thu, Jan 30, 2014 at 11:50:35AM +0530, Kashyap Chamarthy wrote: >>> - Single `make` job timing to compile everything: >>> >>> real 31m9.792s >>> user 17m18.359s >>> sys 13m17.868s >> >> For comparison, on the _host_, the same single `make` job timing: >>

On Thu, Jan 30, 2014 at 04:34:04PM +0530, Kashyap Chamarthy wrote: > On 01/30/2014 03:58 PM, Richard W.M. Jones wrote: > >>> - `make -k check` is still running as I write this, albeit > >>> a bit slow. > >> > >> This just finished (in the container): > >> > >> [. . .] > >> grep -v -E

tl;dr - Is anybody "running" a Fedora system via systemd-nspawn under CentOS? Long version: Before CentOS 7, I used chroot to create "lightweight containers" where I could cleanly add extra repos and/or software without the risk of "polluting" my main system (and potentially ending up in dependency hell). The primary driver for this was MythTV, which has dozens of

On Thu, Jan 30, 2014 at 05:07:23PM +0530, Kashyap Chamarthy wrote: > On 01/30/2014 04:38 PM, Daniel P. Berrange wrote: > > [. . .] > > >> > >> Despite reading from the `systemd-nspawn` man page: > >> > >> ". . .kernel modules may not be loaded from within the container." > >> > >> I purposefully tried from inside the

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

??? ??? systemd-nspawn fails in C7 with ???? ??? ------------ nspawn error -------- ??? sudo? systemd-nspawn ??? Spawning namespace container on /mnt/usb (console is /dev/pts/1). ??? Init process in the container running as PID 1799. ??? Failed to open system bus: No such file or directory ??? Failed to open system bus: No such file or directory ??? Container failed with error code 254. ???

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 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

On 01/30/2014 04:38 PM, Daniel P. Berrange wrote: [. . .] >> >> Despite reading from the `systemd-nspawn` man page: >> >> ". . .kernel modules may not be loaded from within the container." >> >> I purposefully tried from inside the container: > > With container based virt there is only one kernel image, Noted, that's one of the main

On 7/3/19 8:21 AM, Sven Schwedas via samba wrote: > 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 that's very sensitive to instances leaving and joining the > domain seems the antithesis to docker's philosophy. > Docker would be a terrible choice for this;

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

Hi all, It seems RH will deprecate LXC (https://access.redhat.com/articles/1365153) and will go to docker way (or maybe I am totally wrong). Is this true?? Will be systemd-nspawn a lightweight replacement for LXC containers?? Thanks. -- Greetings, C. L. Martinez

https://bugzilla.netfilter.org/show_bug.cgi?id=1210 Bug ID: 1210 Summary: nftables gets confused by user namespaces when meta skuid is used Product: nftables Version: unspecified Hardware: All OS: All Status: NEW Severity: critical Priority: P5 Component: nft

On 2015-11-18 19:41, Warren Young wrote: > On Nov 18, 2015, at 1:20 PM, Kwan Lowe <kwan.lowe at gmail.com> wrote: try systemd-nspawn and use it instead of virtualizing, will save you some bits of memory.

Hi! I with my colleagues from Samsung trying to run systemd in Linux container. I saw that the others are experimenting in this topic, so I would like to present the results of my work and tests, perhaps it will be helpful to others. As the prototype I used a manual written by Daniel: https://www.berrange.com/posts/2013/08/12/running-a-full-fedora-os-inside-a-libvirt-lxc-guest/ After many

I have a container rootfs that I use to keep all work-related stuff. This container was originally created by lxd (which creates all containers for use with user namespacing), but now I decided to start using libvirt for container management since I already use it for virtual machines, which will spare me from dealing with multiple hypervisor technologies. I managed to create a working domain xml

On 7/4/19 12:49 PM, Joachim Lindenberg wrote: > * I am not (yet) familiar with LXD or nspawn. Do you have any pointer on how Samba DC works with LXD? > I've only used LXD for containerizing web applications so far.

On Wed, Feb 26, 2014 at 05:24:03PM +0100, Dariusz Michaluk wrote: [. . .] > If all login attempts are rejected, please boot host machine with audit=0 > > # vi /etc/default/grub > GRUB_CMDLINE_LINUX=" [...] audit=0 [...]" IIUC, this is no longer needed with systemd 209 and above. I just did a quick test[1] with systemd-210-2.fc21.x86_64