Commit graph

1229 commits

Author SHA1 Message Date
Austin Seipp d3fad881d6
firecracker: 0.15.0 -> 0.15.2
Signed-off-by: Austin Seipp <aseipp@pobox.com>
2019-04-22 11:52:40 -05:00
Vincent Demeester 6adf0f3e9a
containerd: 1.2.5 -> 1.2.6
Signed-off-by: Vincent Demeester <vincent@sbr.pm>
2019-04-09 20:05:38 +02:00
Vladimír Čunát a6dd84a126
Merge #57951: qemu: apply CVE-2019-3812 patch 2019-04-07 11:23:20 +02:00
lewo 79016d9f40
Merge pull request #58732 from r-ryantm/auto-update/open-vm-tools
open-vm-tools: 10.3.5 -> 10.3.10
2019-04-06 19:29:35 +02:00
Vincent Demeester 91fc821cc1
podman: 1.1.2 -> 1.2.0
Signed-off-by: Vincent Demeester <vincent@sbr.pm>
2019-04-05 16:56:37 +02:00
markuskowa 3eecb297bc
Merge pull request #58936 from bzizou/charliecloud
charliecloud: init at 0.9.8
2019-04-04 14:43:36 +02:00
Bruno Bzeznik 8a298f8d5a charliecloud: init at 0.9.8 2019-04-04 14:16:48 +02:00
R. RyanTM 475ea05064 open-vm-tools: 10.3.5 -> 10.3.10
Semi-automatic update generated by
https://github.com/ryantm/nixpkgs-update tools. This update was made
based on information from
https://repology.org/metapackage/open-vm-tools/versions
2019-04-01 21:24:10 -07:00
Vincent Demeester 28a2dd8024
runc: 1.0.0-rc6 -> 1.0.0-rc7
Signed-off-by: Vincent Demeester <vincent@sbr.pm>
2019-03-29 11:12:04 +01:00
Andreas Rammhold c7d7c6fc41
qemu: apply CVE-2019-3812 patch 2019-03-20 11:15:41 +01:00
aszlig 12efcc2dee
Merge overlayfs fix, LTS kernel bump and test
In Linux 4.19 there has been a major rework of the overlayfs
implementation and it now opens files in lowerdir with O_NOATIME, which
in turn caused issues in our VM tests because the process owner of QEMU
doesn't match the file owner of the lowerdir.

The crux here is that 9p propagates the O_NOATIME flag to the host and
the guest kernel has no way of verifying whether that flag will lead to
any problems beforehand.

There is ongoing work to possibly fix this in the kernel, but it will
take a while until there is a working patch and consensus.

So in order to bring our default kernel back to 4.19 and of course make
it possible to run newer kernels in VM tests, I'm merging a small QEMU
patch as an interim solution, which we can drop once we have a working
fix in the next round of stable kernels.

Now we already had Linux 4.19 set as the default kernel, but that was
subsequently reverted in 048c36ccaa
because the patch we have used was the revert of the commit I bisected a
while ago.

This patch broke overlayfs in other ways, so I'm also merging in a VM
test by @bachp, which only tests whether overlayfs is working, just to
be on the safe side that something like this won't happen in the future.

Even though this change could be considered a moderate mass-rebuild at
least for GNU/Linux, I'm merging this to master, mainly to give us some
time to get it into the current 19.03 release branch (and subsequent
testing window) once we got no new breaking builds from Hydra.

Cc: @samueldr, @lheckemann

Fixes: https://github.com/NixOS/nixpkgs/issues/54509
Fixes: https://github.com/NixOS/nixpkgs/issues/48828
Merges: https://github.com/NixOS/nixpkgs/pull/57641
Merges: https://github.com/NixOS/nixpkgs/pull/54508
2019-03-19 00:15:51 +01:00
Jason Samsa a7147c868f update xhyve to tip of master 2019-03-18 17:39:18 -05:00
aszlig 4c1ddb3a57
qemu: Apply interim fix for overlayfs + O_NOATIME
Our VM tests and everything related to our virtualisation infrastructure
is currently broken if used with kernel 4.19 or later.

The reason for this is that since 4.19, overlayfs uses the O_NOATIME
flag when opening files in lowerdir and this doesn't play nice with the
way we pass the Nix store to our QEMU guests.

On a NixOS system, paths in the Nix store are typically owned by root
but the QEMU process is usually run by an ordinary user. Using O_NOATIME
on a file where you're not the owner (or superuser) will return with
EPERM (Operation not permitted).

This is exactly what happens in our VM tests, because we're using
overlayfs in the guests to allow writes to the store.

Another implication of this is that the default kernel version for NixOS
19.03 has been reverted to Linux 4.14.

Work on getting this upstream is still ongoing and the patch I posted
previously was incomplete, needs rework and also some more review from
upstream maintainers - in summary: This will take a while.

So instead of rushing in a kernel patch to nixpkgs, which will affect
all users of overlayfs, not just NixOS VM tests, I opted to patch QEMU
for now to ignore the O_NOATIME flag in 9p.

I think this is also the least impacting change, because even if you
care about whether access times are written or not, you get the same
behaviour as with Linux 4.19 in conjunction with QEMU.

Signed-off-by: aszlig <aszlig@nix.build>
Fixes: https://github.com/NixOS/nixpkgs/issues/54509
2019-03-18 13:34:30 +01:00
Vincent Demeester 115dde6d33
containerd: 1.2.4 -> 1.2.5
Signed-off-by: Vincent Demeester <vincent@sbr.pm>
2019-03-14 17:05:29 +01:00
Jascha Geerds ffedc3e4a9 misc: Remove myself from list of maintainers
Unfortunately I don't have the time anymore to maintain those
packages.
2019-03-12 23:50:52 +01:00
Florian Franzen 871c1d5bb1 virtmanager: Fix gobject-introspection (#57385) 2019-03-12 22:29:45 +01:00
Michael Raskin fdeb864cc8
Merge pull request #57498 from r-ryantm/auto-update/virt-viewer
virt-viewer: 7.0 -> 8.0
2019-03-12 15:28:30 +00:00
R. RyanTM 8f92b77ab4 virt-viewer: 7.0 -> 8.0
Semi-automatic update generated by
https://github.com/ryantm/nixpkgs-update tools. This update was made
based on information from
https://repology.org/metapackage/virt-viewer/versions
2019-03-12 02:09:33 -07:00
Wael M. Nasreddine eee09b103c
docker: export GOCACHE for all platforms 2019-03-11 09:59:10 -07:00
Vincent Demeester 54cf5b4bbf containerd: 1.2.2 -> 1.2.4 (#56947)
Signed-off-by: Vincent Demeester <vincent@sbr.pm>
2019-03-08 22:56:00 +01:00
Vincent Demeester 1bd0655e6d podman: 1.1.0 -> 1.1.2 (#56945)
Signed-off-by: Vincent Demeester <vincent@sbr.pm>
2019-03-08 22:31:58 +01:00
lewo f5462b19d5
Merge pull request #56513 from vdemeester/update-podman
Update podman
2019-03-05 21:12:51 +01:00
Jörg Thalheim 27cb0669c6
Merge pull request #56500 from kalbasit/nixpkgs_add-support-go-1-12
go_1_12: init at go 1.12
2019-03-04 14:22:27 +00:00
jD91mZM2 4901af69c5 x11docker: v5.4.1 -> v5.4.4 (#56570) 2019-03-04 13:38:19 +01:00
Wael M. Nasreddine 6ef04cabd4
go_1_12: init at go 1.12 2019-03-02 14:24:17 -08:00
R. RyanTM d047e1e397 docker-compose: 1.23.1 -> 1.23.2
Semi-automatic update generated by
https://github.com/ryantm/nixpkgs-update tools. This update was made
based on information from
https://repology.org/metapackage/docker-compose/versions
2019-03-01 18:16:02 -08:00
Frederik Rietdijk 2fcb11a244 Merge staging-next into master 2019-03-01 09:06:20 +01:00
Vincent Demeester 42a79f7bc2
podman: 1.0.0 -> 1.1.0
Signed-off-by: Vincent Demeester <vincent@sbr.pm>
2019-02-28 11:54:53 +01:00
Vincent Demeester e8a4d2a2be
conmon: unstable-2018-11-28 -> unstable-2019-02-15
Signed-off-by: Vincent Demeester <vincent@sbr.pm>
2019-02-28 11:25:24 +01:00
Averell Dalton d6c2fe76ed nvidia-docker: init at 2.0.3
nvidia_x11 and persistenced were modified to provide binaries which can be
mounted inside a docker-container to be executed there.

most ldconfig-based discovery of bundled nvidia libraries is patched out

ldconfig itself is patched to be able to deal with patchelf'ed libraries
See https://sourceware.org/bugzilla/show_bug.cgi?id=23964
2019-02-27 09:56:03 +01:00
Frederik Rietdijk c2eac6741b Merge master into staging-next 2019-02-24 09:19:12 +01:00
Florian Klink 29d7e7a0c6 virtualbox: 5.2.22 -> 5.2.26 (#56210) 2019-02-22 17:55:47 -08:00
Austin Seipp d011a91b70
firecracker: 0.14.0 -> 0.15.0
Signed-off-by: Austin Seipp <aseipp@pobox.com>
2019-02-22 13:23:46 -06:00
Vladimír Čunát 71f4ba29a3
Merge branch 'master' into staging-next
Hydra nixpkgs: ?compare=1506218
2019-02-22 17:51:01 +01:00
Vladimír Čunát 4ba49d3d6c
Merge #55988: treewide meta.platforms: linux -> unix 2019-02-22 07:59:34 +01:00
Frederik Rietdijk e2cd07b997 Merge staging-next into staging 2019-02-21 07:54:33 +01:00
zimbatm 288f353cdb
firecracker: 0.13.0 -> 0.14.0 2019-02-20 21:16:30 +01:00
Michael Weiss 5a4c8092c0
dynamips: 0.2.19 -> 0.2.20 2019-02-20 20:36:39 +01:00
Matthew Bauer b1bbd94bb6 Merge remote-tracking branch 'NixOS/master' into staging 2019-02-18 20:36:48 -05:00
Frederik Rietdijk 815b77cbe6 Merge master into staging-next 2019-02-18 14:18:04 +01:00
Freezeboy 8f87a61de2 Replace platforms.linux with platforms.darwin for expressions that compile on darwin too (too restrictive platforms) 2019-02-18 10:56:58 +01:00
Justin Bedő 05ab1a6e5a
Merge branch 'master' into singularity 2019-02-17 21:49:37 +00:00
Vladimír Čunát f7f1a2f54e
Merge branch 'master' into staging-next
A mass darwin rebuild from master (#55784).
2019-02-17 08:05:24 +01:00
Jaka Hudoklin fcf505ad09
Merge pull request #55803 from r-ryantm/auto-update/virt-manager
virtmanager: 2.0.0 -> 2.1.0
2019-02-16 13:29:21 +01:00
Maximilian Bosch 3784198856
Merge pull request #55723 from jD91mZM2/x11docker
x11docker: init at 5.4.1
2019-02-16 10:27:42 +01:00
Frederik Rietdijk fd48a94b62 Merge staging-next into staging 2019-02-16 09:30:46 +01:00
Frederik Rietdijk 6fe10d2779 Merge master into staging-next 2019-02-16 09:29:54 +01:00
Samuel Dionne-Riel f8eef26991
Merge pull request #55732 from oxij/tree/move-defaults-to-package-files-mostly-pulse
all-packages.nix: move defaults to package files continues
2019-02-15 17:49:01 -05:00
jD91mZM2 5a00711ef8
x11docker: init at 5.4.1 2019-02-15 17:16:42 +01:00
R. RyanTM 912751bad8 virtmanager: 2.0.0 -> 2.1.0
Semi-automatic update generated by
https://github.com/ryantm/nixpkgs-update tools. This update was made
based on information from
https://repology.org/metapackage/virt-manager/versions
2019-02-14 23:22:42 -08:00