diff options
| author | Patryk Wychowaniec <wychowaniec.patryk@gmail.com> | 2021-02-26 17:14:08 +0100 |
|---|---|---|
| committer | Patryk Wychowaniec <wychowaniec.patryk@gmail.com> | 2021-02-26 17:48:49 +0100 |
| commit | 336ef2de99197dd9c07b302685dc9e6282fa5b55 (patch) | |
| tree | 37c3eb96823750ef2dd985c3ab8862c2bb5f91cb /pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch | |
| parent | 5f1345a30318cf9559e58576dff8c5d3e4d77a62 (diff) | |
nixos/containers: allow containers with long names to create private networks
Launching a container with a private network requires creating a
dedicated networking interface for it; name of that interface is derived
from the container name itself - e.g. a container named `foo` gets
attached to an interface named `ve-foo`.
An interface name can span up to IFNAMSIZ characters, which means that a
container name must contain at most IFNAMSIZ - 3 - 1 = 11 characters;
it's a limit that we validate using a build-time assertion.
This limit has been upgraded with Linux 5.8, as it allows for an
interface to contain a so-called altname, which can be much longer,
while remaining treated as a first-class citizen.
Since altnames have been supported natively by systemd for a while now,
due diligence on our side ends with dropping the name-assertion on newer
kernels.
This commit closes #38509.
systemd/systemd#14467
systemd/systemd#17220
https://lwn.net/Articles/794289/
Diffstat (limited to 'pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch')
0 files changed, 0 insertions, 0 deletions
