Minikube automount relies on a VM disk to be mounted (usually /dev/sda)
to provide .ssh credentials.
This commit adds a dependency on systemd-udev-settle to ensure that all devices
(including disks) are up and available before executing the mount
script.
We use systemd-udev-settle
https://github.com/systemd/systemd/blob/master/units/systemd-udev-settle.service.in
To ensure this. Note that in the above link, we can read a comment
stating that systemd-udev-settle is used to ensure a populated /dev
during bootup, which is exaclty what we want.
Signed-off-by: David Genest <david.genest@gmail.com>
Simple management tool for containers and images
"podman shares state with crio and so has the
capability to debug pods/images created by crio"
https://github.com/projectatomic/libpod/pull/145
This change adds gluster and heketi dependencies to buildroot config,
that is dm_snapshot, dm_thin_pool and XFS kernel modules, XFS tools,
and gluster itself.
linux is upgraded to 4.16, binutils is upgraded to 2.30, and
libelf is installed for the newer kernel.
Other configuration changes are changes in defaults and ordering.
Now using glibc 2.27. systemd 237, and Go 1.10.
vbox-guest is removed because it's upstream as of linux 4.16.
More on buildroot at https://git.buildroot.net/buildroot/tree/CHANGES
Right now the cri-o socket is placed in `/var/run/crio.sock`, this
commit changes it to `/var/run/crio/crio.sock` which is similar to
upstream.
Signed-off-by: Suraj Deshmukh <surajd.service@gmail.com>
Also, this fixes the version output from `kubectl describe node`.
Now it shows:
```
[...]
System Info:
Machine ID: 41af387f4d4e4a3eabcdd2454a7e17f9
System UUID: B5BA9F83-3476-4B4A-943A-81E7A3953234
Boot ID: 7e616123-fa50-4fa9-8f47-88b2a09fbb81
Kernel Version: 4.9.13
OS Image: Buildroot 2017.02
Operating System: linux
Architecture: amd64
Container Runtime Version: cri-o://1.0.3
Kubelet Version: v1.8.0
Kube-Proxy Version: v1.8.0
[...]
```
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
This adds an environment variable file for crio.service to source.
And a step for the buildroot provisioner to write flags, initially just
insecure-registry.
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
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>
The current implementation assumes that we already have docker running.
This switches it to not remove any previous docker configuration
(since there isn't any), and uses our native file transfer utils
instead of the printf commands.
The docker daemon initially starts up in the ISO, only to be stopped
and replaced by minikube's custom configuration. This removes the
initial unit, so that docker doesn't automatically start up until
minikube restarts it with its configuration.
This is an attempt to address #1518. It does actually fix#1518, but breaks much of Kubernetes. :) Don't merge this, I'm just creating a PR that people can play with if they're interested in taking it further.
This rebases minikube-iso to the release 2017-02.
A change in buildroot required the introduction of a `external.desc` as
multiple external trees are supported in modern buildroot versions. This
required change is described here [0].
[0] https://buildroot.org/downloads/manual/manual.html#br2-external-converting
The existing isolinux.cfg was not included in the config and thus
ignored, include it.
The 4.9.13 kernel included in buildroot 2017-02 is not compatible with
VBox guest additions 5.1.6, thus bump guest additions to 5.1.18.
The defconfig of 4.9.13 has been cleaned up.
systemd 232 included in buildroot 2017-02 is incompatible with docker <
17.03 without boot parameter systemd.legacy_systemd_cgroup_controller=yes
Signed-off-by: Thomas Graf <tgraf@suug.ch>
On the initial build run on a new system, the $(shell ...) variant fails
to provide any output for inline substitution and you end up with the
error:
```
gpg: `--verify-files' is not a valid long keyID
```
Using backticks will provide the desired output on the first run on a
system.
Journalctl has not been logging properly in the minikube-iso because of
the absence of /var/log on startup. This is an issue now that we are
using systemd for localkube. This commit links and persists the directory
/var/log like we do for other folders.
Thomas Strömberg
Akihiro Suda
Anders F Björklund
David Genest
Sven Anderson
yanxuean
Aaron Prindle
dlorenc
ijl
AdamDang
Suraj Deshmukh
Vincent Batts
Matt Rickard
Praveen Kumar
Matt Rickard
dlorenc
Bryan Larsen
Jakub Gocławski
Dale Hamel
Thomas Graf
Dongsu Park
Tom von Schwerdtner
Sergiusz Urbaniak