summaryrefslogtreecommitdiff
path: root/units/systemd-nspawn@.service.in
AgeCommit message (Collapse)Author
2016-02-26Don't escape the name of the container in instances ofElias Probst
When using `%I` for instances of `systemd-nspawn@.service`, the result will be `systemd-nspawn` trying to launch a container named e.g. `fedora/23` instead of `fedora-23`. Using `%i` instead prevents escaping `-` in a container name and uses the unmodified container name from the machine store.
2015-11-16nspawn: set TasksMax= for containers to 8192 by defaultLennart Poettering
2015-10-22units: also whitelist "blkext" block devices for nspawn serviceLennart Poettering
/dev/loop*p* block devices are of the "blkext" subsystem, not of loop, hence whitelist this too. Fixes #1446
2015-10-03nspawn: fix --image= when nspawn is run as serviceLennart Poettering
nspawn needs access to /dev/loop to implement --image=, hence grant that in the service file. Fixes #1446.
2015-09-06units: make sure that .nspawn files override the default settings in ↵Lennart Poettering
systemd-nspawn@.service
2015-05-19units: make sure systemd-nspawn@.slice instances are actually located in ↵Lennart Poettering
machine.slice https://plus.google.com/112206451048767236518/posts/SYAueyXHeEX
2015-05-11units: order nspawn containers after network.targetLennart Poettering
This way we know that any bridges and other user-created network devices are in place, and can be properly added to the container. In the long run this should be dropped, and replaced by direct calls inside nspawn that cause the devices to be created when necessary.
2015-04-28nspawn: make sure we install the device policy if nspawn is run as unit as ↵Lennart Poettering
on the command line
2015-02-13units: turn on --network-veth by default for systemd-nspawn@.serviceLennart Poettering
Given the recent improvements in networkd, it's probably the better default now.
2014-12-29units: rework systemd-nspawn@.service unitLennart Poettering
- Unescape instance name so that we can take almost anything as instance name. - Introduce "machines.target" which consists of all enabled nspawns and can be used to start/stop them altogether - Look for container directory using -M instead of harcoding the path in /var/lib/container
2014-11-21nspawn: Add try-{host,guest} journal link modesMartin Pitt
--link-journal={host,guest} fail if the host does not have persistent journalling enabled and /var/log/journal/ does not exist. Even worse, as there is no stdout/err any more, there is no error message to point that out. Introduce two new modes "try-host" and "try-guest" which don't fail in this case, and instead just silently skip the guest journal setup. Change -j to mean "try-guest" instead of "guest", and fix the wrong --help output for it (it said "host" before). Change systemd-nspawn@.service.in to use "try-guest" so that this unit works with both persistent and non-persistent journals on the host without failing. https://bugs.debian.org/770275
2014-11-05core: introduce new Delegate=yes/no property controlling creation of cgroup ↵Lennart Poettering
subhierarchies For priviliged units this resource control property ensures that the processes have all controllers systemd manages enabled. For unpriviliged services (those with User= set) this ensures that access rights to the service cgroup is granted to the user in question, to create further subgroups. Note that this only applies to the name=systemd hierarchy though, as access to other controllers is not safe for unpriviliged processes. Delegate=yes should be set for container scopes where a systemd instance inside the container shall manage the hierarchies below its own cgroup and have access to all controllers. Delegate=yes should also be set for user@.service, so that systemd --user can run, controlling its own cgroup tree. This commit changes machined, systemd-nspawn@.service and user@.service to set this boolean, in order to ensure that container management will just work, and the user systemd instance can run fine.
2014-07-03nspawn: when running in a service unit, use systemd for restartsLennart Poettering
THis way we can remove cgroup priviliges after setup, but get them back for the next restart, as we need it.
2014-05-30units: use KillMode=mixed for systemd-nspawn@.serviceJonathan Liu
This causes the container to shut down cleanly when the service is stopped.
2014-02-11units: make use of nspawn's --keep-unit switch in systemd-nspawn@.serviceLennart Poettering
2013-11-09man,units: fix installation of systemd-nspawn@.service and add exampleZbigniew Jędrzejewski-Szmek
2013-09-17nspawn: update unit fileLennart Poettering
ControlGroup= is obsolete, so let's drop it from the default nspawn unit file.
2013-04-30units: add an easy-to-use unit template file systemd-nspawn@.service for ↵Lennart Poettering
running containers as system services