On Wed, Apr 20, 2016 at 6:50 PM, Harald Dunkel wrote:
> Hi folks,
>
> AFAIR the idea of the containers was to provide isolation
> between the host and the user-space instances.
>
> Are we loosing this with systemd support?
What makes you think that?
The host only needs systemd cgroup mount, it d
Have you ever start lxc on that host succesfully before? Or is this a
first attempt?
IIRC on my centos 6.6:
- I need newer kernel. Went with kernel ml
(http://elrepo.org/linux/kernel/el6/x86_64/RPMS/) which had 4.4 back
then.
It had /sys/fs/cgroup, so I can mount tmpfs there (with fstab), and
moun
Hi,
Commit fd51a89b60d06f1f207196e5fe6e8e8f7bea3beb [support arguments in
lxc.init_cmd] introduced the function split_init_cmd() in lxccontainer.c.
Compiling this with gcc 5.3.0 (archlinux) and -Werror on uninitialized
variables causes a build failure (full error is attached):
On 20/04/16 18:50, 술욱 wrote:
What do you, users and devs, prefer, Btrfs or ZFS?
i am dev and sysadmin too, and i prefer btrfs now (see below)
My current setup is 2TB md raid1, Ext4. I was going to format Btrfs
next weekend, but after reading the following link, I'm not so sure:
https://ins
Turns out that it was cgroup was mounted under /cgroup, so I was able to
create the folder there and mount it. However the container shows the same
error:
[root@devhost fs]# mount -t cgroup -o none,name=systemd cgroup
/cgroup/systemd/
[root@devhost fs]# grep cg /proc/mounts
cgroup /cgroup/cpuset
It actually depends on what on how you want to store you data, here is a
complete comparison between both:
https://www.diva-portal.org/smash/get/diva2:822493/FULLTEXT01.pdf
--
Alan Hoffmeister
https://twitter.com/alan_hoff
https://github.com/alanhoff
https://keybase.io/alanhoff
2016-04-20 20:55
I can tell you that when I tried btrfs in good faith, I was faced with
bugs that kept lxc from working correctly. Simply moving /var to ext4
fixed everything. I haven't tried zfs yet, but it ought to be very
well supported for lxc.
Jake
On Wed, Apr 20, 2016 at 4:50 PM, 술욱 wrote:
> Hello list,
Hello list,
What do you, users and devs, prefer, Btrfs or ZFS?
My current setup is 2TB md raid1, Ext4. I was going to format Btrfs
next weekend, but after reading the following link, I'm not so sure:
https://insights.ubuntu.com/2016/02/16/zfs-is-the-fs-for-containers-in-ubuntu-16-04/
Is there
I cloned the master branch and rebuilt it. Did 'make uninstall' for the
previous lxc-2.0.0 and installed new version. However it still throws the
same error. Also tried to create the systemd folder:
[root@devhost lxc]# mkdir -p /sys/fs/cgroup/systemd
mkdir: cannot create directory `/sys/fs/cgroup/
Hi,
edit that script to do 'set -x', so that we can see what the script
is doing in the container debug log.
Quoting Muneeb Ahmad (muneeb.ganda...@gmail.com):
> lxcfs=2.0.0
> lxc=2.0.0.rc9
> And the contents of lxc.mount.hook are;
>
> #!/bin/sh -e
>
>
> # We're dealing with mount entries, so e
> cgfsng.c:all_controllers_found:431 - no systemd controller mountpoint found
> lxc-start: cgfsng.c: all_controllers_found: 431 no systemd controller
> mountpoint found
This is known. You can either run from git head to get the patch which
fixes this, or just make sure to have a name=systemd cgro
Any ideas?
Has this anything to do with CGManager?
and this is what lxcfs status show:
*●* lxcfs.service - FUSE filesystem for LXC
Loaded: loaded (/lib/systemd/system/lxcfs.service; enabled; vendor
preset: enabled)
Active: *active (running)* since Wed 2016-04-20 11:17:05 PKT; 53min ago
M
lxcfs=2.0.0
lxc=2.0.0.rc9
And the contents of lxc.mount.hook are;
#!/bin/sh -e
# We're dealing with mount entries, so expand any symlink
LXC_ROOTFS_MOUNT=$(readlink -f *${LXC_ROOTFS_MOUNT}*)
# /proc files
if [ -d /var/lib/lxcfs/proc/ ]; then
for entry in /var/lib/lxcfs/proc/*; do
Hello,
I have a host system running Oracle Linux 6.7 and installed lxc 2.0.0 from
source tarball.
I created a node using:
# lxc-create -n node2 -t download
Distribution: Oracle Linux 6, amd64
I cannot start the node:
[root@devhost ~]# lxc-start -n node2 -l debug -F -o /dev/stdout
lxc-st
I am using succesfully LXC 1.1.5 on Centos, but wish to install 2.0. The
missing link is
git clone git://pkgs.fedoraproject.org/lxc.git
this part does not work with version 2.0.0
maybe somebody can ask the Fedora people to work a little harder.
rpm -qa | grep lxc
lxc-libs-1.1.5-1.el7.centos.1.x86_
The best alternative is probably libvirt lxc. That's what we use. We had
started trying lxc/lxd under CentOS 7 and hit various issues. The
project has been tabled for now and we're sticking with libvirt lxc...
On 04/20/2016 10:05 AM, Saint Michael wrote:
That is what I am afraid of.
On Wed, A
That is what I am afraid of.
On Wed, Apr 20, 2016 at 12:46 PM, jjs - mainphrame
wrote:
> From everything I've seen, it would be an uphill battle.
>
> IMHO, just as Ubuntu is the optimal distro for lxc/lxd, Centos 7 goes
> with openvz, and works really well with it.
>
> Jake
>
> On Wed, Apr 20, 2
From everything I've seen, it would be an uphill battle.
IMHO, just as Ubuntu is the optimal distro for lxc/lxd, Centos 7 goes
with openvz, and works really well with it.
Jake
On Wed, Apr 20, 2016 at 8:35 AM, Saint Michael wrote:
> I have been scratching my head on how to install LXC 2.0 on top
I have been scratching my head on how to install LXC 2.0 on top of Centos
7.
has anybody accomplished this task?
___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo/lxc-users
Hi folks,
AFAIR the idea of the containers was to provide isolation
between the host and the user-space instances.
Are we loosing this with systemd support?
Regards
Harri
___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.lin
Hi,
>>> On Wed, 20 Apr 2016 09:13:26 +0200
in message "Re: [lxc-users] sysvinit with cgroup namespace"
Harald Dunkel-san wrote:
> I tried, but it did not work:
> # grep /sys/fs/cgroup /etc/fstab
> systemd /sys/fs/cgroup cgroup none,name=systemd
I can start a container on
On Wed, Apr 20, 2016 at 2:13 PM, Harald Dunkel wrote:
> I tried, but it did not work:
>
> # grep /sys/fs/cgroup /etc/fstab
> systemd /sys/fs/cgroup cgroup none,name=systemd
Should be
# grep systemd /proc/mounts
cgroup /sys/fs/cgroup/systemd cgroup rw,relatime,clone_children,name=systemd 0 0
name
Hi Serge,
On 04/06/16 17:18, Serge Hallyn wrote:
> Quoting KATOH Yasufumi (ka...@jazz.email.ne.jp):
>>
>> Will we be able to start a container on sysvinit with cgroup namespace
>> in the future release?
>
> mkdir /sys/fs/cgroup
> mount -t cgroup -o none,name=systemd systemd /sys/fs/cgroup
>
> Yo
23 matches
Mail list logo
