f8bc4a61ea
Upgrade runc from v1.0.0-rc92 to v1.0.0-rc93
2021-03-17 20:01:55 +01:00
ac63d9ed18
Upgrade Docker, from 19.03.14 to 20.10.0
...
runc v1.0.0-rc92
containerd v1.4.3
2020-12-09 21:13:25 +01:00
d8e39a2dc5
Set the ISO go target environment properly
2020-10-02 08:49:17 +02:00
4c8e88ab47
Upgrade Buildroot to 2020.02 LTS with Linux 4.19
...
Do the kernel upgrade separately, for easier ISO testing
Use the same kernel version as was in "2019.02.x" branch
2020-09-27 14:11:32 +02:00
857b693f57
Revert "The config flag for go packages were both changed"
...
Need to use the old config flag again for the old Buildroot
This reverts commit 661feaca3f
2020-07-06 08:49:43 +02:00
8fcfaf4a66
Merge pull request #8187 from afbjorklund/buildroot-2020.02
...
Buildroot 2020.02
2020-06-09 15:07:59 -07:00
de5a1fae02
Improve version output of the runc command
...
Currently it is showing the "dirty" status of buildroot,
due the build script picking the wrong git repository...
runc version 1.0.0-rc10
commit: dc9208a3303feef5b3839f4323d9beb36df0a9dd-dirty
2020-05-19 07:36:05 +02:00
661feaca3f
The config flag for go packages were both changed
...
This caused the go-depending packages to be skipped
2020-05-17 19:55:46 +02:00
c977faf22e
Upgrade Docker, from 19.03.5 to 19.03.6 ( #6618 )
...
runc v1.0.0-rc10
containerd v1.2.12
2020-02-13 15:44:14 -07:00
c8b30a566d
Fix the version number output of runc
...
And make the build more standardized, use the make target
2020-01-04 15:55:27 +01:00
f486f96711
Update runc hash
2019-11-20 13:17:18 -08:00
cdc0a38102
Update containerd and runc
2019-11-15 10:16:06 -08:00
8bea8e719f
Upgrade Docker, from 18.09.6 to 18.09.7
...
runc v1.0.0-rc8-0-g425e105
containerd v1.2.6
2019-07-01 21:56:15 +02:00
b31c66c807
Link runc dynamically, avoid docker-runc install
...
Static linking doesn't work with the systemd cgroup manager.
The latest docker package now uses the standard runc program.
2019-06-04 07:13:59 +02:00
5927bf874d
Upgrade Docker, from 18.06.3-ce to 18.09.5
...
Stop installing docker-runc, docker-containerd and docker-containerd-ctr
Instead use the upstream runc, containerd and ctr (after upgrading them)
runc v1.0.0-rc6-69-g2b18fe1
containerd v1.2.5
2019-05-04 18:16:37 +02:00
bab67c46fc
runc 0a012df
...
CVE-2019-5736
2019-02-13 20:26:43 +01:00
28d0edda80
Install upstream runc into /usr/bin/docker-runc
2019-01-18 08:07:23 -08:00
0219c67612
Pull in opencontainers/runc#1962 by updating to runc HEAD
2019-01-16 11:06:49 -08:00
e677c9639d
runc 0fdc908
2017-12-14 08:54:36 -08:00
2788714cc5
minikube-iso: add cri-o runtime
...
https://github.com/kubernetes-incubator/cri-o
Updated the runc version to its latest master commit.
Got crio into the automounter to get off the tmpfs
This feature bubbles up to the minikube command by reusing the
`--container-runtime=` flag, by enabling the value of "`crio`"
(`minikube start --container-runtime=crio`), while the flags/config
passed to localkube are more like k8s (`--container-runtime=remote
--remote-runtime-endpoint=/var/run/crio.sock`)
This is mostly ready for review. It is still lacking having
--insecure-registry plumbed through, but for now the policy.json is
open.
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2017-09-27 09:12:15 -04:00
Anders F Björklund
Medya Ghazizadeh
Harsimran Singh Maan
Thomas Stromberg
ijl
Vincent Batts