| commit | 9956e72c6c0b4f6436dc9493bc213965ee0cc191 | [log] [tgz] |
|---|---|---|
| author | Lorenz Brun <lorenz@nexantic.com> | Wed Mar 24 18:48:55 2021 +0100 |
| committer | Leopold Schabel <leo@nexantic.com> | Tue Apr 13 11:03:53 2021 +0200 |
| tree | 7842ac67432e3a187dda6a2dcb46d11088934159 | |
| parent | dca59d924dac4345099e5acd99405b5451d29cdb [diff] |
Add Loop Device package This adds Loop device support in our Linux kernel and adds a Go package for working with them. It also drive-by adds a pre-mounted tmpfs to ktest as that is quite useful in a lot of situations. Test Plan: Comes with ktests. X-Origin-Diff: phab/D745 GitOrigin-RevId: fa06bcdddc033efb136f56da3b4a91159273bf88
This is the main repository containing the source code for the Monogon Project.
⚠️ This is pre-release software that happens to be publicly available. Nothing to see here, please move along.
Our build environment requires a working Podman binary (your distribution should have one).
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, which enables full autocompletion for external dependencies and generated code. 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. On IntelliJ 2020.3 or later, you need to install a beta release of the plugin.
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:
scripts/bin/bazel run //:launch
Run a kubectl command:
scripts/bin/bazel run //metropolis/cli/dbg -- kubectl describe
Run tests:
scripts/bin/bazel test //...