similar to: systemd-nspawn will replace lxc

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

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

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

Hi. Another week, another experiment ;) I was trying to run systemd user session for non-root user, for example darek (uid=1000), operation failed with error: systemd[26]: pam_unix(systemd-user:session): session opened for user darek by (uid=0) systemd[1]: Started Login Service. systemd[26]: Failed to create root cgroup hierarchy: Permission denied systemd[26]: Failed to allocate manager

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/ 'audit=0' on Kernel command line. (NOTE: There's work in progress[2] in upstream Kernel to fix

On Mon, Aug 10, 2015 at 09:50:04PM +0100, Mark Clarkson wrote: > Hi, > I noticed that libvirt-lxc will be deprecated for RedHat: > > "Future development on the Linux containers framework is now based on the > docker command-line interface. libvirt-lxc tooling may be removed in a > future release of Red Hat Enterprise Linux (including Red Hat Enterprise > Linux 7) and

On Mon, Aug 10, 2015 at 09:50:04PM +0100, Mark Clarkson wrote: >Hi, >I noticed that libvirt-lxc will be deprecated for RedHat: > >"Future development on the Linux containers framework is now based on >the docker command-line interface. libvirt-lxc tooling may be removed >in a future release of Red Hat Enterprise Linux (including Red Hat >Enterprise Linux 7) and should not

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

On Tue, Aug 11, 2015 at 08:31:02AM +0200, Martin Kletzander wrote: > On Mon, Aug 10, 2015 at 09:50:04PM +0100, Mark Clarkson wrote: > >Hi, > >I noticed that libvirt-lxc will be deprecated for RedHat: > > > >"Future development on the Linux containers framework is now based on > >the docker command-line interface. libvirt-lxc tooling may be removed > >in

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/

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

Hi, I noticed that libvirt-lxc will be deprecated for RedHat: "Future development on the Linux containers framework is now based on the docker command-line interface. libvirt-lxc tooling may be removed in a future release of Red Hat Enterprise Linux (including Red Hat Enterprise Linux 7) and should not be relied upon for developing custom container management applications." -

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 Wed, Feb 12, 2014 at 12:51:10PM +0100, arnaud gaboury wrote: > Dear all, > > I am slowly building a Arch Linux VM guest on my Arch Linux host. > > The guest machine is now built and is recognized as shown by this command : > > gabx@hortensia ➤➤ ~ % machinectl list > MACHINE CONTAINER SERVICE > dahlia container

Dear all, I am slowly building a Arch Linux VM guest on my Arch Linux host. The guest machine is now built and is recognized as shown by this command : gabx@hortensia ➤➤ ~ % machinectl list MACHINE CONTAINER SERVICE dahlia container nspawn 1 machines listed. I an following the libvirt.org documentation. Now, according this page[1] about lxc

On Fri, Sep 18, 2015 at 7:38 AM, Sandro Bonazzola <sbonazzo at redhat.com> wrote: > > > On Thu, Sep 17, 2015 at 6:15 PM, C. L. Martinez <carlopmart at gmail.com> > wrote: >> >> On Thu, Sep 17, 2015 at 6:06 PM, George Dunlap <dunlapg at umich.edu> wrote: >> > On Thu, Sep 17, 2015 at 3:19 PM, C. L. Martinez <carlopmart at gmail.com> >>

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