Skip to content
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.

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

[Bug]: sandbox stops #5139

Closed
1 task done
stevenbaert opened this issue Nov 20, 2024 · 8 comments
Closed
1 task done

[Bug]: sandbox stops #5139

stevenbaert opened this issue Nov 20, 2024 · 8 comments
Labels
bug Something isn't working Stale Inactive for 30 days

Comments

@stevenbaert
Copy link

stevenbaert commented Nov 20, 2024

Is there an existing issue for the same bug?

  • I have checked the existing issues.

Describe the bug and reproduction steps

My Docker config below, sandbox stops without any logfile created.
Maybe my yaml file needs modification?

version: '3.8'

services:
openhands-app:
image: docker.all-hands.dev/all-hands-ai/openhands:0.14
container_name: openhands01
ports:
- "3003:3000" # Maps container port 3003 to host port 3003
environment:
SANDBOX_RUNTIME_CONTAINER_IMAGE: "docker.all-hands.dev/all-hands-ai/runtime:0.14-nikolaik"
ANTHROPIC_API_KEY: "REDACTED"
volumes:
- /var/run/docker.sock:/var/run/docker.sock
- /path/to/your/data:/data
restart: always
extra_hosts:
- "host.docker.internal:host-gateway"

sandbox-runtime:
image: docker.all-hands.dev/all-hands-ai/runtime:latest
container_name: sandbox-runtime01
volumes:
- /var/run/docker.sock:/var/run/docker.sock
restart: always

OpenHands Installation

Docker command in README

OpenHands Version

0.14

Operating System

Linux

Logs, Errors, Screenshots, and Additional Context

No response


Note: OpenHands starts, but when I ask to execute something it stalls on "Preparing to start container..."

@stevenbaert stevenbaert added the bug Something isn't working label Nov 20, 2024
@stevenbaert
Copy link
Author

No logs for sandbox, in other container no errors.

@mamoodi
Copy link
Collaborator

mamoodi commented Nov 20, 2024

Did your configuration used to work on a previous version? Does just running the docker command from the README work by any chance?

@stevenbaert
Copy link
Author

Note: after 20 min sandbox did not start. Or does it only start after logging in/starting a project (giving input)?

Your question, why would Docker command be any different than yaml? Just asking since I really wouldn't know 😊

@mamoodi
Copy link
Collaborator

mamoodi commented Nov 20, 2024

I guess my question is, if you run this, does it work at all?

docker pull docker.all-hands.dev/all-hands-ai/runtime:0.14-nikolaik

docker run -it --rm --pull=always \
    -e SANDBOX_RUNTIME_CONTAINER_IMAGE=docker.all-hands.dev/all-hands-ai/runtime:0.14-nikolaik \
    -e LOG_ALL_EVENTS=true \
    -v /var/run/docker.sock:/var/run/docker.sock \
    -p 3000:3000 \
    --add-host host.docker.internal:host-gateway \
    --name openhands-app \
    docker.all-hands.dev/all-hands-ai/openhands:0.14

@stevenbaert
Copy link
Author

Thanks but docker run is not an option for me, even if it would work. At the end yaml or docker run are the same just other way of setting up.
I run my Dockers on Synology via container app and really do not want to ssh into it, though I could as last resort.

Probably yes there is a config issue in my yaml and that's whay I would like to find out.

So translating your input to yaml is below. I can give that a go.

version: '3.9'
services:
openhands-app:
image: docker.all-hands.dev/all-hands-ai/openhands:0
container_name: openhands-app
pull_policy: always
environment:
- SANDBOX_RUNTIME_CONTAINER_IMAGE=docker.all-hands.dev/all-hands-ai/runtime:0.14-nikolaik
- LOG_ALL_EVENTS=true
volumes:
- /var/run/docker.sock:/var/run/docker.sock
ports:
- "3003:3000"
extra_hosts:
- "host.docker.internal:host-gateway"
stdin_open: true
tty: true
restart: "no" # Mimics --rm behavior, no restart on exit

@stevenbaert
Copy link
Author

Update: my project/container openhands was stopped and today I see 3(!) new sandboxes running (not the openhands container nore the sandbox) .... Not sure what happened. Deleted them but now I am puzzled what mechanism behind it is.

Copy link
Contributor

This issue is stale because it has been open for 30 days with no activity. Remove stale label or comment or this will be closed in 7 days.

@github-actions github-actions bot added the Stale Inactive for 30 days label Dec 24, 2024
Copy link
Contributor

github-actions bot commented Jan 1, 2025

This issue was closed because it has been stalled for over 30 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jan 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working Stale Inactive for 30 days
Projects
None yet
Development

No branches or pull requests

2 participants