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

Unable to start stopped containers #175

Closed
miversen33 opened this issue Dec 23, 2023 · 1 comment
Closed

Unable to start stopped containers #175

miversen33 opened this issue Dec 23, 2023 · 1 comment
Assignees
@miversen33
Labels
bug Something isn't working
Milestone
v1.15 (Preplannin...

Comments

@miversen33
Copy link
Owner

In main you can click on a stopped container and the docker provider will prompt you asking if you wish to start the container. In v1.15, you cannot do this. Infact, neotree just treats the container as a directory. Kinda bad, we should fix that.
@miversen33 miversen33 added the bug Something isn't working label Dec 23, 2023
@miversen33 miversen33 self-assigned this Dec 23, 2023
@miversen33
Copy link
Owner Author

Turns out past Mike accounted for this and actually properly accounted for this exact situation in the new ASP model. The issue is that our neo-tree extension is not handling that bubble up response properly

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@miversen33 miversen33

Labels
bug Something isn't working
Projects
None yet
Milestone
v1.15 (Preplanning for v1.2)
Development

When branches are created from issues, their pull requests are automatically linked.

175-handle-connect-com miversen33/netman.nvim
1 participant
@miversen33