jesseduffield / jesseduffield/lazydocker

[BUG] No containers to restart

Open
#258 2 comments 0 reactions 0 assignees View on GitHub
bug
Dominant language
Go
Stars
52.8k
Forks
1.7k
PR merge metrics
No merged PRs in 30d

Description

**Describe the bug**
A clear and concise description of what the bug is.

When I try to restart one of my services in my docker-compose file I get the following screen:
![image](https://user-images.githubusercontent.com/5251028/119802740-19840900-bedf-11eb-9b75-4ce08a3b19d5.png)

I started lazydocker as follow `lazydocker -f .docker/docker-compose.yaml -f .docker/docker-compose.override.yaml`
We're using a specific project layout with our projects and a nice helper function for handling our docker stuff, this bash-function eventually calls lazydocker with the above layout but for some reason restarting of the services doesn't work...

**To Reproduce**
Steps to reproduce the behavior:
1. Start lazydocker with specific docker files
2. try to restart a service using the menu and choosing restart (also tried the restart options)

**Expected behaviour**
A clear and concise description of what you expected to happen.
My container will be restarted

**Screenshots**
If applicable, add screenshots to help explain your problem.
![image](https://user-images.githubusercontent.com/5251028/119803167-7b447300-bedf-11eb-9909-9285dc5b76d6.png)

**Desktop (please complete the following information):**
- OS: Linux Ubuntu 18.04 running in WSL 2
- Lazydocker Version [e.g. v0.1.45]: 0.12
- The last commit id if you built project from sources (run : ```git rev-parse HEAD```)

**Additional context**
Add any other context about the problem here.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.