>> I actually had a cgroup-lite uprev in flight which has now been sent
>> to the list. I also have plans to uprev LXC in the next week or so,
>> along with making some changes, such as dropping the lxc-setup package
>> which has its roots from early iterations of the systemd/sysvinit
>> split, which can be done differently now. If I find the time to get
>> this done you should see the series soon.
>> to the list. I also have plans to uprev LXC in the next week or so,
>> along with making some changes, such as dropping the lxc-setup package
>> which has its roots from early iterations of the systemd/sysvinit
>> split, which can be done differently now. If I find the time to get
>> this done you should see the series soon.
The uprev cgroup-lite works fine. Now I don't have to mount systemd manually. Thank you for that.
> Just to follow up on this. With the cgroup-lite change sent and merged yesterday
> I am able to create and run a container using the lxc busybox template.
> I am able to create and run a container using the lxc busybox template.
> I needed to update the template to 'binary_copy passwd' and adjust the
> 'chmod' path for this from '/bin/passwd' to '/usr/bin/passwd'.
How do you change the lxc-busybox-template exactly? What code do I have to change into binary_copy passwd?
Do you mean the chmod path in the function configure_busybox() { ... # passwd exec must be setuid
chmod +s $rootfs/bin/passwd ...} ?
Do you mean the chmod path in the function configure_busybox() { ... # passwd exec must be setuid
> Along with manually tweaking the memory cgroup (via 'echo 1 > /sys/fs/cgroup/memory/memory. use_hierarchy).
In my case this isn't possible: write error: Device or resource busy.
> I will not consider
> digging in to fix these until I confirm they are still an issue after
> the LXC uprev.
> The following are the only changes to my local.conf
> ---
> MACHINE = "qemux86-64"
> DISTRO_FEATURES += "virtualization"
> PACKAGE_CLASSES = "package_ipk"
> IMAGE_INSTALL_append += "cgroup-lite lxc"
> ---
I got it working on the machine = "qemux86", too (Krogoth). I needed to add under meta-virtualization/recipes- core/busybox a new
Config-file with "CONFIG_INIT=y" in it. I can't access the running container with lxc-console, but with lxc-attach it works fine.
Config-file with "CONFIG_INIT=y" in it. I can't access the running container with lxc-console, but with lxc-attach it works fine.
In my minnowboard image (machine = "intel-corei7-64" modified with PREFERRED_PROVIDER_virtual/
this isn't enough. I got the error:
[12208.261387] devpts: called with bogus options
lxc-start: conf.c: lxc_create_tty: 3284 No such file or directory - failed to create pty #0
lxc-start: conf.c: lxc_setup: 3800 failed to create the ttys
lxc-start: conf.c: lxc_create_tty: 3284 No such file or directory - failed to create pty #0
lxc-start: conf.c: lxc_setup: 3800 failed to create the ttys
lxc-start: start.c: do_start: 819 failed to setup the container
lxc-start: sync.c: __sync_wait: 52 An error occurred in another process (expected sequence number 2)
lxc-start: sync.c: __sync_wait: 52 An error occurred in another process (expected sequence number 2)
Any ideas?
In lxc-checkconfig there is Multiple /dev/pts instances: missing (in qemux it is enabled). CONFIG_DEVPTS_MULTIPLE_
-- _______________________________________________ meta-virtualization mailing list [email protected] https://lists.yoctoproject.org/listinfo/meta-virtualization
