| commit | 7b82227c87f477e9d986d648b8ad63f4268dde3b | [log] [tgz] |
|---|---|---|
| author | Lorenz Brun <lorenz@nexantic.com> | Wed Feb 03 17:03:41 2021 +0100 |
| committer | Lorenz Brun <lorenz@nexantic.com> | Wed Feb 03 17:03:41 2021 +0100 |
| tree | bd4f8afb09a40f4217709f956c2344c67f95e660 | |
| parent | 378a4455aedda838f60c546e55199092f24952ed [diff] |
Drop legacy kubelet log path It looks like the Kubernetes update broke E2E tests on the EROFS stack because of some change to how the legacy log dir is handled. Kubelet currently just crashes because it can't mkdir /var/log/containers. This directory is apparently only used by fluentd for log collection in upstream E2E tests and with dockershim, both of which we don't care about. So let's just nuke it. Test Plan: Fixes things on top of the EROFS stack X-Origin-Diff: phab/D700 GitOrigin-RevId: 45b7f76a61b7234845ab55fcfbc37a66f69fe065
This is the main repository containing Monogon's public source code, including Metropolis.
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.
The following steps are necessary:
Install Google's 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.
Use File → Import Bazel project... to create a new project from .bazelproject.
After running the first sync, everything should now resolve in the IDE, including generated code.
It's strongly recommend to use our project presets for file watchers and other IDE features. Run this command and re-open the project in order to install them:
bazel run intellij/localconfig $(pwd)
Launch the node:
bazel run //:launch
Run a kubectl command:
bazel run //metropolis/cli/dbg -- kubectl describe