Debian Codegraph @

debian/NEWS

raw
1 lxc (1:7.0.0-1) unstable; urgency=medium
2
3 LXC 7 has removed support for a few deprecated kernel features:
4
5 * CGroupV1
6 * Kernels without PIDFD support
7 * Kernels without the new mount API
8
9 -- Mathias Gibbens <[email protected]> Thu, 30 Apr 2026 19:13:10 +0000
10
11 lxc (1:4.0.6-2) unstable; urgency=medium
12
13 A new way of handling unprivileged containers starting and attachment has
14 been made available through the lxc-unpriv-start and lxc-unpriv-attach
15 commands. See /usr/share/doc/lxc/README.Debian.gz for more details.
16
17 -- Pierre-Elliott Bécue <[email protected]> Fri, 11 Jun 2021 15:12:15 +0200
18
19 lxc (1:4.0.2-1~1) experimental; urgency=medium
20
21 Major changes in the Debian packaging:
22
23 1. lxc-net is now enabled by default, and newly created containers will
24 have networking by default.
25
26 Major changes between LXC 3.0.x and LXC 4:
27
28 1. CGroupV2 support:
29 LXC 4 supports the unified CGroup hierarchy, which means that the
30 containers will now be able to handle a booted system with an init like
31 systemd using the unified CGroup hierarchy. This has implications
32 regarding the unprivileged containers, as a standard user can't get an
33 empty CGroup by themselves. In that specific situation, libpam_cgfs is
34 useless.
35
36 A solution to run an unprivileged container as a standard non-root user
37 is to use systemd-run:
38
39 `systemd-run --user --scope -p "Delegate=yes" lxc-start container-name`
40
41 The user instance of systemd will delegate an empty CGroup available and
42 manipulable properly by the container.
43 2. The default AppArmor profile now denies access to /proc/acpi/. This was
44 already the case in Debian but has been merged upstream.
45 3. config: Add lxc.autodev.tmpfs.size configuration key:
46 LXC supports creating a useable minimal /dev directory for the container by
47 setting lxc.autodev = 1 in the container’s config file. To do this LXC sets up
48 a tmpfs mount on /dev. This tmpfs mount could not be restricted in prior
49 releases. Now it is possible to set a limit on the size of the tmpfs mount by
50 setting lxc.autodev.tmpfs.size to the number of bytes that the tmpfs should be
51 restricted to use.
52 4. config: Add lxc.selinux.context.keyring key
53 This allows one to specify the selinux context to be used for the keyring
54 the container uses.
55 5. config: Add lxc.keyring.session
56 Setting this to 1 (default) will cause LXC to create a new session keyring.
57
58 Other changes:
59 1. Freezer support in CGroupV2:
60 As part of the cgroup2 support work for LXC 4.0 support for cgroup2’s
61 implementation of the freezer controller has been added. It allows one
62 to poll until the cgroup is frozen or unfrozen making freezing and
63 unfreezing container’s way more reliable than before.
64 2. file utils: Add fopen_cached() and fdopen_cached
65 These helpers first read a whole file and then make it available as a
66 stream to be read via regular file-based libc apis. This makes LXC’s
67 handling of various files more robust where the underlying file can
68 change while it is read.
69 3. PIDfd support
70 LXC 4.0 fully supports the new pidfd kernel api the LXC team has merged
71 in the upstream Linux kernel. The pidfd of the container’s init process
72 can be requested via c->init_pidfd(c).
73 4. memory utils: Add new cleanup api
74 LXC 4.0 expands the usage of the compiler’s cleanup attribute by introducing
75 new internal apis to define and call cleanup macros for complex resource
76 allocations. Significant results in decreasing bugs around file
77 descriptor and memory leaks by switching to this new way of cleaning up
78 resources have been observed.
79 5. lxc-usernsexec: Make it easy to map own uid
80 The lxc-usernsexec binary now finds a default mapping as specified in
81 /etc/subuid and /etc/subgid and writes it via newuidmap and newgidmap.
82 6. seccomp: Add s390 support
83 LXC 4.0’s seccomp implementation now supports s390 as architecture.
84 7. syscalls: Improve manual syscall implementations
85 Whenever a given syscall is not supported or exposed by the underlying C
86 library of the system LXC will define syscall stubs for important
87 syscalls or new features it deems extremely valuable. This used to be
88 done by checking for __NR_<syscall-name> being defined. But
89 __NR_<syscall-name> being defined depended on the correct headers for
90 the currently running kernel LXC was compiled on being installed and
91 would be problematic whenever LXC was compiled on a system running an
92 older kernel but used or deployed on systems that use a new kernel. In
93 such scenarios LXC could not make use of new kernel features even though
94 it should. Definitions for __NR_<syscall-name> are introduced whenever
95 the system does not define it already and it is a supported architecture
96 (which is basically any architecture). This results in a better handling
97 of kernel <-> header version mismatches and compilation <-> deployment
98 kernel mismatches.
99 8. network: Improved network device creation and removal
100 The way network devices are created, tracked, moved between network
101 namespaces, and are removed has been reworked. This makes the low-level
102 network management way more reliable.
103 9. network: Allow moving wireless devices
104 LXC allowed to move wireless network devices (nl80211) into containers. This
105 was broken for a while. With 4.0 the ability to move wireless network devices
106 is restored and improved.
107
108 -- Pierre-Elliott Bécue <[email protected]> Thu, 15 Apr 2020 22:44:32 +0200
109
110 lxc (1:3.1.0+really3.0.3-6) unstable; urgency=medium
111
112 LXC 3 got some significant changes from LXC 2.
113
114 1. The configuration files use different variables. A userland script
115 lxc-update-config is available to update automatically your
116 configuration files. An automatic update is possible and offered by
117 debconf during the upgrade of lxc version < 3.0.2 to lxc version >=
118 3.0.2. Mind that this update will only work for privileged containers
119 with configurations present in /var/lib/lxc/*/config and any other
120 container will not be updated.
121 2. AppArmor support in Debian has increased, thus preventing some systemd
122 isolation features to work in LXC 3.0.X. Debian has backported some
123 patches from LXC 3.1 that, along with some configurations in a
124 container, will allow systemd isolation features to work.
125
126 The required configuration parameters are the ones which follow:
127 lxc.apparmor.profile = generated
128 lxc.apparmor.allow_nesting = 1
129
130 These parameters are provided in the `/etc/lxc/default.conf` file
131 shipped with LXC 3. Hence, any newly created container will have these
132 parameters set properly, except if you alter the aforementioned file.
133
134 WARNING: Note that with these parameters, unprivileged containers won't
135 be able to start. lxc.apparmor.profile must be set to either
136 'unconfined' or to 'lxc-container-default-cgns'. This can be done either
137 in the unprivileged container configuration file or in the user's
138 .config/lxc/default.conf file.
139 3. lxc-templates is deprecated by upstream. The new way of building
140 containers is via their distrobuilder software. This software isn't in
141 Debian Buster, and thus, we still provide lxc-templates. If you relied
142 on it (eg, with lxc.include parameter in some configuration file), you
143 should install lxc-templates in case it doesn't come by itself (via
144 recommends). Otherwise you may experience issues after the upgrade.
145
146 -- Pierre-Elliott Bécue <[email protected]> Sat, 09 Mar 2019 13:09:05 +0100
147
148 lxc (1:1.1.5-1) unstable; urgency=medium
149
150 LXC before 1.1 did silently ignore lxc.aa_profile if the kernel did
151 not have the AppArmor mount feature (by checking for the existence of
152 /sys/kernel/security/apparmor/features/mount/mask).
153
154 As of LXC 1.1 it will error out with the following message in the log:
155 Incomplete AppArmor support in your kernel
156 If you really want to start this container, set
157 lxc.aa_allow_incomplete = 1 in your container configuration file
158
159 Debian does not ship with AppArmor enabled in the kernel by default,
160 so this should not affect default installs. However if you have enabled
161 AppArmor, your containers will fail to start after the upgrade.
162
163 Please add "lxc.aa_allow_incomplete = 1" to your configuration to
164 start AppArmor-secured containers until we have full support in the
165 kernel.
166
167 -- Evgeni Golov <[email protected]> Sun, 31 Jan 2016 18:22:40 -0200
168