| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
| |
service type
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
It doesn't have a start script, so it hasn't worked at all in
a long time.
|
| |
|
|
| |
`pkg.lxd.bin` does
|
| |
|
|
|
|
|
|
|
| |
We need to use wrapped modprobe, so that it finds the right
modules. Docker needs modprobe to load overlay kernel module
for example.
This fixes an an error starting docker if the booted system's kernel
version is different from the /run/current-system profile's one.
|
| |
|
|
|
|
|
|
| |
Otherwise systemd gets confused and forgets about device units after
reloading.
https://github.com/NixOS/nixops/issues/391
https://github.com/systemd/systemd/issues/3423
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Since systemd version 230, it is required to have a machine-id file
prior to the startup of the container. If the file is empty, a transient
machine ID is generated by systemd-nspawn.
See systemd/systemd#3014 for more details on the matter.
This unbreaks all of the containers-* NixOS tests.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
Cc: @edolstra
Closes: #15808
|
| |
|
|
|
|
|
| |
The existence of $root/var/lib/private/host-notify as a socket
prevented a bind mount:
container foo[8083]: Failed to create mount point /var/lib/containers/foo/var/lib/private/host-notify: No such device or address
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This allows setting options for the same LUKS device in different
modules. For example, the auto-generated hardware-configuration.nix
can contain
boot.initrd.luks.devices.crypted.device = "/dev/disk/...";
while configuration.nix can add
boot.initrd.luks.devices.crypted.allowDiscards = true;
Also updated the examples/docs to use /disk/disk/by-uuid instead of
/dev/sda, since we shouldn't promote the use of the latter.
|
| |
|
|
| |
There is a generic boot.loader.timeout option.
|
| |\ |
|
| | | |
|
| | |
| |
| |
| | |
This includes the binutils mass rebuild.
|
| | | |
|
| | |
| |
| |
| |
| | |
This also fixes the incorrect use of 'dev' outputs from
config.nix.package and pkgs.systemd.
|
| |\ \
| | |
| | |
| | |
| | | |
kampfschlaefer/feature/hostbridge_and_ipv6_for_containers
containers: hostbridge and IPv6
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Without the templating (which is still present for imperative containers), it
will be possible to set individual dependencies. Like depending on the network
only if the hostbridge or hardware interfaces are used.
Ported from #3021
|
| | | |
| | |
| | |
| | |
| | |
| | | |
This allows the containers to have their interface in a bridge on the host.
Also this adds IPv6 addresses to the containers both with bridged and unbridged
network.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
They are compressed nowadays.
Not sure if these are really needed since nobody noticed they were
broken, but anyway...
|
| | |/
|/|
| |
| |
| | |
The former is deprecated and doesn't handle compressed kernel modules,
so all current usages of it are broken.
|
| | | |
|
| |\ \
| | |
| | |
| | |
| | |
| | | |
Comparison to master evaluations on Hydra:
- 1255515 for nixos
- 1255502 for nixpkgs
|
| | |/ |
|
| |\|
| |
| |
| |
| |
| | |
This is mainly to get the update of bootstrap tools.
Otherwise there were mysterious segfaults:
https://github.com/NixOS/nixpkgs/pull/7701#issuecomment-203389817
|
| | |
| |
| |
| |
| |
| | |
NixOps has infrequent releases, so it's not the best place for keeping
the list of current AMIs. Putting them in Nixpkgs means that AMI
updates will be delivered as part of the NixOS channels.
|
| | |\
| | |
| | | |
xe-guest-utilities: init at 6.2.0
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
use mkEnableOption
use sha256
add xe-guest-utilities to module-list.nix
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
We now generate a qcow2 image to prevent hitting Hydra's output size
limit. Also updated /root/user-data -> /etc/ec2-metadata/user-data.
http://hydra.nixos.org/build/33843133
|
| | | | |
|
| | |/ |
|
| |\|
| |
| |
| |
| | |
Beware that stdenv doesn't build. It seems something more will be needed
than just resolution of merge conflicts.
|
| | |
| |
| |
| |
| |
| |
| |
| | |
Previously this was done in three derivations (one to build the raw
disk image, one to convert to OVA, one to add a hydra-build-products
file). Now it's done in one step to reduce the amount of copying
to/from S3. In particular, not uploading the raw disk image prevents
us from hitting hydra-queue-runner's size limit of 2 GiB.
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
bug is fixed
|
| | |
| |
| |
| | |
before SSHD generates the host keys
|
| | |
| |
| |
| |
| |
| |
| | |
azure-agent: add option for verbose logging
azure-agent: disable ssh host key regeneration
azure-common: set verbose logging on
azure-image: increase size to 30GB
|
| | | |
|
| |\|
| |
| |
| |
| | |
The kde-5 stuff still didn't merge well.
I hand-fixed what I saw, but there may be more problems.
|
| | |
| |
| |
| | |
working generation and add helpful comments
|
| | |
| |
| |
| | |
27016659046a8f8e7b4fd61ecbceaf9f5e306258 broke this.
|
| | |\
| | |
| | | |
azure: package qemu 2.2.0 to fix VHD creation
|
| | | |
| | |
| | |
| | |
| | | |
This commit packages qemu-220. This package is qemu-2.2.0
and is only used with Azure.
|
| | |/ |
|
| | | |
|
| | |\ |
|
| | |\ \ |
|
| | | | | |
|