Linux containers implementation
It provides commands to create and manage containers. It contains a
full featured container with the isolation/virtualization of the pids,
the ipc, the utsname, the mount points, /proc, /sys, the network and it
takes into account the control groups. It is very light, flexible, and
provides a set of tools around the container like the monitoring with
asynchronous events notification, or the freeze of the container. This
package is useful to create Virtual Private Server, or to run isolated
applications like bash or sshd.
- Developed at Virtualization:containers
- Sources inherited from project openSUSE:Factory
-
1
derived packages
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout openSUSE:Factory:RISCV/lxc && cd $_ - Create Badge
Refresh
Refresh
Source Files
Revision 68 (latest revision is 107)
Dominique Leuenberger (dimstar_suse)
accepted
request 428745
from
Dominique Leuenberger (dimstar_suse)
(revision 68)
- setcap has been moved to /usr/sbin (boo#998326). - update lxc to 2.0.4 - add 0001-bdev-use-correct-overlay-module-name.patch - add 0002-cleanup-tools-remove-name-from-lxc-top-usage-message.patch - add 0003-cleanup-whitespaces-in-option-alignment-for-lxc-exec.patch - add 0004-Use-full-GPG-fingerprint-instead-of-long-IDs.patch - add 0005-tools-move-rcfile-to-the-common-options-list.patch - add 0006-tools-set-configfile-after-load_config.patch - add 0007-doc-add-rcfile-to-common-opts.patch - add 0008-doc-Update-Korean-lxc-attach-1.patch - add 0009-doc-Add-rcfile-to-Korean-common-opts.patch - add 0010-doc-Add-rcfile-to-Japanese-common-opts.patch - add 0011-tools-use-exit-EXIT_-everywhere.patch - add 0012-tools-unify-exit-calls-outside-of-main.patch - add 0013-utils-Add-mips-signalfd-syscall-numbers.patch - add 0014-seccomp-Implement-MIPS-seccomp-handling.patch - add 0015-seccomp-Add-mips-and-mips64-entries-to-lxc_config_pa.patch - add 0016-seccomp-fix-strerror.patch - add 0017-confile-add-more-archs-to-lxc_config_parse_arch.patch - add 0018-seccomp-add-support-for-s390x.patch - add 0019-seccomp-remove-double-include-and-order-includes.patch - add 0020-seccomp-non-functional-changes.patch - add 0021-templates-use-fd-9-instead-of-200.patch - add 0022-templates-fedora-requires-openssl-binary.patch - add 0023-tools-use-boolean-for-ret-in-lxc_device.c.patch - add 0024-c-r-use-proc-self-tid-children-instead-of-pidfile.patch - add 0025-c-r-Fix-pid_t-on-some-arches.patch - add 0026-templates-Add-mips-hostarch-detection-to-debian.patch - add 0027-cleanup-replace-tabs-wth-spaces-in-usage-strings.patch
Comments 8
Is maintaining of the package limited to downstream (/backported?) patches for the 2.0.9 version? Are there any plans to update to the latest one?
Hi,
no, I was actually planning to get the 3.x update in. But as many things regarding packaging changed betweeen 2.0.x and 3.x, I never got around to finalize things.
I have been preparing some stuff for LXC 3.0 and 3.1 here, including the python3 python-lxc package that replaces the code that was in the lxc package in 2.0.x: home:ojkastl_buildservice:LXC_Vanilla_stable-3.0 home:ojkastl_buildservice:LXC_Vanilla_stable-3.1
I was reworking python-lxc and will soon submit it to d:l:p, as soon as I find time for that.
Thanks for the reply. It's important for me to know that the work is under way. Thank you for all the effort you put into it :)
Unfortunately LXC 2.0.9 does not build with Python 3.7 on Tumbleweed. LXC users need to compile LXC themselves. If the 3.X update needs some time, I suggest to fix the LXC 2.0.9 package first. I created a merge request for LXC 2.0.9: https://build.opensuse.org/request/show/671861
SR has been accepted.
I've submitted a 3.x update as well as a package for LXD. I can deal with maintenance if you have too many other things to maintain.
I've got here an obsolete and incompatible since 3.0 lxc.aa_allow_incomplete = 1 at /usr/share/lxc/config/common.conf.d/30-openSUSE-apparmor.conf belonging to the lxc package. It prevents containers from starting but gives quite an accurate error message. Is this an adequate place to tell you that? I looked around just a bit and haven't found a bug tracker here Thanks for the update though!
This isn't a bug tracker -- please submit bugs to https://bugs.opensuse.org/ (or https://bugzilla.opensuse.org/). I will take a look at that...