Skip to content

Add Setup.md#216

Merged
LittleHuba merged 1 commit intomainfrom
brem_add_setup
Mar 20, 2026
Merged

Add Setup.md#216
LittleHuba merged 1 commit intomainfrom
brem_add_setup

Conversation

@bemerybmw
Copy link
Contributor

No description provided.

@hoppe-and-dreams
Copy link
Contributor

I also added a line in overall readme here: #214

SETUP.md Outdated
## Integration Tests

Prerequisites:
- Docker (Instructions for installing here: https://docs.docker.com/engine/install/)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just a note, I tried with rootless mode ( https://docs.docker.com/engine/security/rootless/ ) it works fine and has less security implications. So it might be worth to note this. (And a question is if we want to officially support rootless mode)

@bemerybmw bemerybmw force-pushed the brem_add_setup branch 3 times, most recently from aaa46f9 to db94056 Compare March 20, 2026 09:24
SETUP.md Outdated
To work around this issue, you can run the following bash script (must be run with sudo!):

```bash
sudo bash actions/unblock_user_namespace_for_linux_sandbox/action_callable.sh
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ahh sorry, the script itself is calling sudo on the right actions. So you don't have to call the script itself with sudo. My mistake...

SETUP.md Outdated

Ubuntu 24.04 introduced the security framework apparmor. The standard configuration of apparmor which also includes unprivileged user namespaces interferes with the bazel sandboxing mechanism and inhibits the linux-sandbox. This affects all bazel tests and potentially any bazel runnables.

To work around this issue, you can run the following bash script (must be run with sudo!):
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe also drop a note that this must be rerun when we update the bazel version.

Comment on lines +16 to +20
if [ $? -ne 0 ]; then
echo "Warning: '${INSTALL_BASE}/linux-sandbox \"/bin/true\"' failed."
else
echo "Success: '${INSTALL_BASE}/linux-sandbox \"/bin/true\"' succeeded."
fi
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Return the exit code from the script to make the CI fail if this check fails.

Suggested change
if [ $? -ne 0 ]; then
echo "Warning: '${INSTALL_BASE}/linux-sandbox \"/bin/true\"' failed."
else
echo "Success: '${INSTALL_BASE}/linux-sandbox \"/bin/true\"' succeeded."
fi
EXIT_CODE=$?
if [ $EXIT_CODE -ne 0 ]; then
echo "Warning: '${INSTALL_BASE}/linux-sandbox \"/bin/true\"' failed."
else
echo "Success: '${INSTALL_BASE}/linux-sandbox \"/bin/true\"' succeeded."
fi
exit $EXIT_CODE

@LittleHuba LittleHuba enabled auto-merge March 20, 2026 11:26
@LittleHuba LittleHuba added this pull request to the merge queue Mar 20, 2026
Merged via the queue into main with commit e0aa4b6 Mar 20, 2026
15 checks passed
@LittleHuba LittleHuba deleted the brem_add_setup branch March 20, 2026 12:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants