docker run with no container errors with "address already in use"
Open
Nobody has claimed this yet.
docker
- Dominant language
- No language data
- Stars
- 17
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
Although docker ps -a showed no container, I got an error saying a port was busy:
docker: Error response from daemon: driver failed programming external connectivity on endpoint determined_kilby (e0dee9e44951f81c547e49aef70bc343b6d091a148cd054c8c927865f0a257b6): Error starting userland proxy: listen tcp 0.0.0.0:8787: bind: address already in use.
What solved it comes from https://stackoverflow.com/a/49657132/5005834
sudo service docker stop
sudo rm /var/lib/docker/network/files/local-kv.db
sudo service docker start
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the reported docker run failure and the docker ps -a, service docker, and /var/lib/docker/network/files/local-kv.db commands mentioned in the issue. The report provides no repository file, test, or acceptance criterion, so a contribution cannot yet be started or verified from the issue alone.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100