commune/bloc

Fork 0

Test bloc inside agent container #2

New issue

Closed

opened 2026-02-24 09:58:54 -08:00 by brad · 3 comments

brad commented

2026-02-24 09:58:54 -08:00

Owner

@intern the new agent sandbox container has been built. tagging you here should have started a new one with bloc available in your environment. can you please respond to this thread with a report of whether or not it's working? ty

@intern the new agent sandbox container has been built. tagging you here should have started a new one with `bloc` available in your environment. can you please respond to this thread with a report of whether or not it's working? ty

intern commented

2026-02-24 09:59:42 -08:00

Owner

bloc CLI Test Report

Status: ❌ Not working

Environment

Container user: sandbox
PATH includes: /usr/local/bin

Issue

The bloc binary is not accessible:

$ which bloc
# returns nothing

$ bloc --version
sh: line 1: bloc: command not found

Root Cause

Found a broken symlink:

$ ls -la /usr/local/bin/bloc
lrwxrwxrwx 1 root root 21 Feb 24 17:21 /usr/local/bin/bloc -> /root/.local/bin/bloc

$ ls -la /root/.local/bin/bloc
ls: cannot access /root/.local/bin/bloc: Permission denied

The symlink points to /root/.local/bin/bloc, but the sandbox user cannot access /root/ (permission denied).

Fix Needed

The symlink target needs to be either:

Placed in a location accessible to the sandbox user (e.g., /usr/local/bin/bloc as the actual binary, not a symlink)
Or the symlink should point to a user-accessible location like /home/agent/.local/bin/bloc

Additional Info

No bloc binary found anywhere in /home/agent tree or other accessible paths.

## bloc CLI Test Report **Status:** ❌ Not working ### Environment - Container user: `sandbox` - PATH includes: `/usr/local/bin` ### Issue The `bloc` binary is not accessible: ```bash $ which bloc # returns nothing $ bloc --version sh: line 1: bloc: command not found ``` ### Root Cause Found a broken symlink: ```bash $ ls -la /usr/local/bin/bloc lrwxrwxrwx 1 root root 21 Feb 24 17:21 /usr/local/bin/bloc -> /root/.local/bin/bloc $ ls -la /root/.local/bin/bloc ls: cannot access /root/.local/bin/bloc: Permission denied ``` The symlink points to `/root/.local/bin/bloc`, but the `sandbox` user cannot access `/root/` (permission denied). ### Fix Needed The symlink target needs to be either: 1. Placed in a location accessible to the `sandbox` user (e.g., `/usr/local/bin/bloc` as the actual binary, not a symlink) 2. Or the symlink should point to a user-accessible location like `/home/agent/.local/bin/bloc` ### Additional Info No `bloc` binary found anywhere in `/home/agent` tree or other accessible paths.

brad commented

2026-02-24 10:11:03 -08:00

Author

Owner

@agent let's fix this within commune/sandbox. bloc should be installed and available within the /usr/local/bin path.

agent commented

2026-02-24 10:12:33 -08:00

Owner

Fixed in commune/sandbox@a220ec2. The issue was that uv tool install created the executable in /root/.local/bin/ with a symlink, which the sandbox user couldn't access properly due to permission constraints.

Changed to uv pip install --system which installs bloc directly to the system Python, creating the executable at /usr/local/bin/bloc (via the console_scripts entry point in pyproject.toml). This makes it accessible to all container users.

The fix is on branch agent/add-bloc-uv-tool in commune/sandbox. Once the container rebuilds, bloc should be available in the sandbox environment at /usr/local/bin/bloc.

Fixed in commune/sandbox@a220ec2. The issue was that `uv tool install` created the executable in `/root/.local/bin/` with a symlink, which the `sandbox` user couldn't access properly due to permission constraints. Changed to `uv pip install --system` which installs bloc directly to the system Python, creating the executable at `/usr/local/bin/bloc` (via the `console_scripts` entry point in pyproject.toml). This makes it accessible to all container users. The fix is on branch `agent/add-bloc-uv-tool` in commune/sandbox. Once the container rebuilds, bloc should be available in the sandbox environment at `/usr/local/bin/bloc`.

brad closed this issue

2026-02-24 10:29:14 -08:00

No labels

No milestone

No project

No assignees

3 participants

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

commune/bloc#2

No description provided.

Rows
Columns