mirror/nixpkgs - Nix packages collection

Age	Commit message (Collapse)	Author	Files	Lines
2022-03-28	treewide: machine -> nodes.machine	Robert Hensing	1	-1/+1

2021-11-21	nixos/qemu-vm: default memorySize 384 -> 1024	Artturin	1	-1/+0
	the default hasn't been changed since 2009 this can improve our test performances nixos/tests: remove explicit memorySize <1024 1024MiB is now the default
2021-10-28	nixos/qemu-vm: Rename pathsInNixDB to additionalPaths	talyz	1	-1/+1
	pathsInNixDB isn't a very accurate name when a Nix store image is built (virtualisation.useNixStoreImage); rename it to additionalPaths, which should be general enough to cover both cases.
2021-02-26	nixos/containers: styling improvements	Patryk Wychowaniec	1	-5/+3

2021-01-10	treewide: simplify pkgs.stdenv.lib -> pkgs.lib	Dominik Xaver Hörl	1	-1/+1
	The library does not depend on stdenv, that `stdenv` exposes `lib` is an artifact of the ancient origins of nixpkgs.
2019-12-08	nixosTests.containers*: port rest to python	Martin Milata	1	-40/+31

2019-01-13	nixos/containers: explicitly set link up on host for extraVeths	elseym	1	-0/+1

2018-10-30	tests/docs: remove remnants of old allowPing default (#49198)	Robin Gloster	1	-1/+0
	This has been defaulting to true since 16.03, we don't need this code anymore, also the note in the documentation has been obsolete for quite a while.
2018-07-20	[bot] nixos/*: remove unused arguments in lambdas	volth	1	-1/+1

2018-02-17	nixos/tests: rename IP addresses/routes options	rnhmjoj	1	-3/+3

2017-02-17	replace ping6 with ping	Jörg Thalheim	1	-1/+1
	reason: after the upgrade of iputils from 20151218 to 20161105 functionality of ping6 and tracepath6 was merged into ping and tracepath. Ping is now mostly a drop-in replacment for ping6, except that selecting a specific interface is done by encoding it into the address (ex.: fe80::1%eth0) rather then specifing it with the `-I` flag.
2016-07-28	containers: add myself to the maintainers of the tests	Arnold Krille	1	-1/+1
	Seems like the right thing to do.
2016-07-28	declarative containers: additional veths	Arnold Krille	1	-0/+103
	With these changes, a container can have more then one veth-pair. This allows for example to have LAN and DMZ as bridges on the host and add dedicated containers for proxies, ipv4-firewall and ipv6-firewall. Or to have a bridge for normal WAN, one bridge for administration and one bridge for customer-internal communication. So that web-server containers can be reached from outside per http, from the management via ssh and can talk to their database via the customer network. The scripts to set up the containers are now rendered several times instead of just one template. The scripts now contain per-container code to configure the extra veth interfaces. The default template without support for extra-veths is still rendered for the imperative containers. Also a test is there to see if extra veths can be placed into host-bridges or can be reached via routing.