I am facing this error whenever I try to use docker
unable to resolve docker endpoint: Invalid proto, expected tcp: http://127.0.0.1:5000
Share and learn in the Docker community.
I am facing this error whenever I try to use docker
unable to resolve docker endpoint: Invalid proto, expected tcp: http://127.0.0.1:5000
Good morning,
what (which command) were you trying before this message appeared?
This message appears for all commands even when I just simply type docker.
Here is a error log while using Docker SDK for python
Traceback (most recent call last):
File "C:\files\appData\Projects\PycharmProjects\AWSDispatch\AWSConfig\temp.py", line 3, in <module>
client = docker.from_env()
File "C:\files\appData\Projects\PycharmProjects\AWSDispatch\.venv\lib\site-packages\docker\client.py", line 94, in from_env
return cls(
File "C:\files\appData\Projects\PycharmProjects\AWSDispatch\.venv\lib\site-packages\docker\client.py", line 45, in __init__
self.api = APIClient(*args, **kwargs)
File "C:\files\appData\Projects\PycharmProjects\AWSDispatch\.venv\lib\site-packages\docker\api\client.py", line 136, in __init__
base_url = utils.parse_host(
File "C:\files\appData\Projects\PycharmProjects\AWSDispatch\.venv\lib\site-packages\docker\utils\utils.py", line 287, in parse_host
raise errors.DockerException(
docker.errors.DockerException: Invalid bind address format: port is required: tcp://http://127.0.0.1:5000
I edited your messages. Please, format your post next time according to the following guide: How to format your forum posts
In short: please, use </>
button to share codes, terminal outputs, error messages or anything that can contain special characters which would be interpreted by the MarkDown filter. Use the preview feature to make sure your text is formatted as you would expect it and check your post after you have sent it so you can still fix it.
Example code block:
```
echo "I am a code."
echo "An athletic one, and I wanna run."
```
I also changed the topic title. Please always chose a title that shortly describes the issue instead of only saying that it is an issue, which is obvios. Thank you.
Regarding the error message it seems pretty clear about that you used the http potocol when it would require tcp protocol. As you cans ee in the error message, tcp was added before the url, so you don’t even need to define the protocol. Just use the IP address and the port.