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.

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

Jump to bottom

[Bug]: Docker containers are not destroyed after closing WS connection on the client #4759

Closed
1 task done
amanape opened this issue Nov 5, 2024 · 1 comment
Closed
1 task done

[Bug]: Docker containers are not destroyed after closing WS connection on the client #4759

amanape opened this issue Nov 5, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@amanape
Copy link
Member

amanape commented Nov 5, 2024

Is there an existing issue for the same bug?

  • I have checked the existing issues.

Describe the bug and reproduction steps

The Docker runtime containers that are started by the app when initiating a session persist even after closing the WS connection in the client (e.g., after returning to the home page). This causes a build-up of unused yet active containers

OpenHands Installation

Docker command in README

OpenHands Version

0.12.2

Operating System

MacOS

Logs, Errors, Screenshots, and Additional Context

image
@amanape amanape added the bug Something isn't working label Nov 5, 2024
@mamoodi
Copy link
Collaborator

mamoodi commented Nov 5, 2024

This PR merged related to fixing this: #4765

Can you confirm it's fixed on latest main now please?

@amanape amanape closed this as completed Nov 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@amanape @mamoodi