Certain commands not streaming full output

[TheFlash2k]

I have the following code setup to run a simple command in my Sandbox template:

def do_run(cmd):
    out = sbx.commands.run(
        cmd, timeout=0, 
        on_stdout=lambda data: print('stdout: ', data),
        on_stderr=lambda data: print('stderr: ', data)
    )
    return out.stdout or out.stderr

Now, I am trying to run a few particular tools such as katana, nuclei (most of the tools are written in Go-Lang).

The problem I am facing is, whenever I try to invoke any of the tools (particularly the tools provided by projectdiscovery or tools written in Golang), they just get stuck. And HARD-STUCK. The only thing I see is their Ascii art and then they just don't run.

In the logs

Whereas, if in the same sandbox, I try to run the command manually:

Another weird issue I face when the command runs for more than 5 mins is (even though the sandbox timeout is 1 hour).

One of the fixes that I did was inside the sandbox_sync/commands/command.py on Line 232.

- args=["-l", "-c", cmd],
+ args=["-c", cmd],

The most weird part is, it did fix the issue for once, but after some time, the fix stopped working. At this point I am lost debugging this issue further and would require some assistance. Also, I have tried other scripts that were written in python, those seem to work fine without any issue. Even tried rustscan and it did work. Only happens for tools written in golang which is absurd because they're elf binaries anyways.

Already tried with and without 2>&1 (I just did this to redirect stderr to stdout for testing)

If I try to run this with quotes around the command itself, I'm assuming it adds the quotes itself so it would do double quotes and hence sets the blob as one whole command and therefore fails

For further context, the e2b.Dockerfile is:

FROM ubuntu:latest

ENV DEBIAN_INTERACTIVE=1
ENV TZ=Asia/Karachi

RUN apt-get update && \
        apt-get install -y golang && \
    apt-get clean && rm -rf /var/lib/apt/lists*

RUN go install -v github.com/projectdiscovery/nuclei/v3/cmd/nuclei@latest
RUN CGO_ENABLED=1 go install github.com/projectdiscovery/katana/cmd/katana@latest && rm -rf /root/.cache/go*

COPY scripts /usr/bin/

WORKDIR /root

[linear]

E2B-2225 Certain commands not streaming full output

[bukacdan]

@mishushakov @TheFlash2k
it seems to be a problem with interactive CLI apps that expect the stdout to be a real terminal. Happened to me with claude code.

Wrapping the command into expect solved the issue for me.

[TheFlash2k]

@bukacdan Thank you so much. This seems to have solved the issue for me now. The way I am executing the command is:

def do_run(cmd):
    script  = f"spawn {cmd}\nexpect eof"
    with open("/tmp/s.exp", "w") as f:
        f.write(script)
    f = open("/tmp/s.exp", "r")
    sbx.files.write("/tmp/s.exp", f)
    f.close()
    out = sbx.commands.run(
        "expect /tmp/s.exp", timeout=0, 
        on_stdout=lambda data: print('stdout: ', data),
        on_stderr=lambda data: print('stderr: ', data)
    )
    return out.stdout or out.stderr

Is there any better way that you'd recommend?

[bukacdan]

I have ended up with the very similar configuration. The temperatures in Cursor are low I guess 😃
But overall it seems like a simple working solution, so I'll keep it this way for now.

[mishushakov]

Hey both,
thanks for your help!

Do you have any suggestions if we could do anything to support such cases better?
Let me know!

[bukacdan]

You could either allow for custom cmd parameter when running the command in sandbox_sync/commands/command.py, so that it doesn't always start with /bin/bash -l -c.

Or if this seems like an interesting use case for yall, you could add a new action, something along sandbox.commands.run_interactive, where you'd add support for commands that require interactive sessions.