| commit | c88c82db8b1a7f8a07782c970e1d0dfb453f9f66 | [log] [tgz] |
|---|---|---|
| author | Lorenz Brun <lorenz@nexantic.com> | Fri May 08 14:35:04 2020 +0200 |
| committer | Lorenz Brun <lorenz@nexantic.com> | Fri May 08 14:35:04 2020 +0200 |
| tree | 22072c4f18e4aaa855577ff0b42a86ef77a9c4cb | |
| parent | 60febd9db40970a31a2f49bdb969897a37c11cc6 [diff] |
Add containerd & gVisor support This adds containerd, CNI, gVisor and all the necessary shims and supporting infrastructure. It also enables all relevant features in the Linux kernel. containerd is designed as a simple supervisor.Runnable. It is not being started yet, this will happen in D497. Split out from feature/kubelet. Test Plan: Has been tested in conjunction with the rest of D497, will be covered by a K8s E2E test there. X-Origin-Diff: phab/D509 GitOrigin-RevId: 92523516b7e361a30da330eb187787e6045bfd17
This is the monorepo storing all of nexantic's internal projects and libraries.
We assume a Fedora host system provisioned using rW, and IntelliJ as the IDE.
For better reproducibility, all builds are executed in containers.
Spinning up: scripts/create_container.sh
Spinning down: scripts/destroy_container.sh
Running commands: scripts/run_in_container.sh <...>
Using bazel using a wrapper script: scripts/bin/bazel <...> (add to your local $PATH for convenience)
This repository is compatible with the IntelliJ Bazel plugin. All commands run inside the container, and necessary paths are mapped into the container.
We check the entire .ijwb project directory into the repository, which requires everyone to use the latest version of both IntelliJ and the Bazel plugin, but eliminates manual setup steps.
The following steps are necessary:
Install Google's official Bazel plugin in IntelliJ.
Add the absolute path to your ~/.cache/bazel-nxt folder to your idea64.vmoptions (Help → Edit Custom VM Options) and restart IntelliJ:
-Dbazel.bep.path=/home/leopold/.cache/bazel-nxt
Set "Bazel Binary Location" in Other Settings → Bazel Settings to the absolute path of scripts/bin/bazel. This is a wrapper that will execute Bazel inside the container.
Open the .ijwb folder as IntelliJ project.
Disable Vgo support for the project.
Run a non-incremental sync in IntelliJ
The plugin will automatically resolve paths for generated files.
If you do not use IntelliJ, you need to use the scripts/bazel_copy_generated_for_ide.sh script to copy files locally.