Skip to content

Document state of linux-sandbox in the container #33

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
nradakovic merged 4 commits into from
Oct 23, 2025
Merged

Document state of linux-sandbox in the container #33

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
7bc9a22
Document state of linux-sandbox in the container
lurtz Oct 6, 2025
f29b113
fix typo
lurtz Oct 7, 2025
2621c0f
Merge branch 'main' into run-privileged
opajonk Oct 10, 2025
2e496b4
Merge branch 'main' into run-privileged
lurtz Oct 14, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
23 changes: 21 additions & 2 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,8 @@ Modifying the content of the container is explained in the [Development](#develo

## Usage

> **NOTE:** There are several development environments which support development containers; most notably [Visual Studio Code](https://code.visualstudio.com), but also [IntelliJ IDEA](https://www.jetbrains.com/idea) and others.
> [!NOTE]
> There are several development environments which support development containers; most notably [Visual Studio Code](https://code.visualstudio.com), but also [IntelliJ IDEA](https://www.jetbrains.com/idea) and others.
> See [here](https://containers.dev/supporting) for a more complete list.
> In the following, we assume that [Visual Studio Code](https://code.visualstudio.com) and its Dev Containers extension is used.
The [Dev Containers extension homepage](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers) has a description how to get up to speed on Windows, macOS and Linux operating systems.
Expand Down Expand Up @@ -43,6 +44,23 @@ Afterwards, Visual Studio Code should show this in the lower left corner of your

![Dev container success](resources/devcontainer_success.png)

### Bazel's `linux-sandbox`

`linux-sandbox` makes use of [Linux user namespaces](https://man7.org/linux/man-pages/man7/user_namespaces.7.html).
These only work for `linux-sandbox` as expected, if the following snippet is added to the `.devcontainer/devcontainer.json`:

```json
"runArgs": [
"--privileged"
]
```

In this case using `--privileged` is [recommended by Bazel](https://bazel.build/docs/sandboxing#sandboxing-strategies),
probably due to lack of alternatives.

> [!NOTE]
> If `linux-sandbox` is not needed, do not add this snippet.

### Inside the Container

Open a Terminal, and - for example - type `bazel build ...` to execute the default build of the repository.
Expand All @@ -58,7 +76,8 @@ Congratulations, you are now a dev container enthusiast 😊.

## Development

> **NOTE:** This is about the development *of the DevContainer*, not about development of Eclipse S-CORE *using* the DevContainer.
> [!NOTE]
> This is about the development *of the DevContainer*, not about development of Eclipse S-CORE *using* the DevContainer.

The [Eclipse S-CORE](https://github.com/eclipse-score) development container is developed using - a development container!
That means, the usage is similarly simple:
Expand Down