Why do bugs always come up when the timing isn't great? I just checking out huginn and n8n. Both looked interesting to automate some daily pain away. While huginn ran without any issues, n8n gave me some headache. Here I hope to avoid the same for someone else!
I've run the following command to get nodemation, short n8n, up:
$ docker run -it --rm --name n8n -p 5678:5678 -v ~/.n8n:/home/node/.n8n n8nio/n8n
Unfortunately this little issue found it's way on my console:
docker: error during connect: Post http://docker:2375/v1.24/containers/create?
name=n8n: dial tcp: lookup docker on 192.168.0.1:53: no such host.
My first hinge was that my hard-disk was running low on free space. A quick df -h relieved me from this worry: There was still plenty of space. But some interesting temporary entries showed up:
$ df -h
[...]
overlay 233G 199G 22G 91%
/var/lib/docker/overlay2/b43aff7ed1bce158f79d70657e83c92debab01caa8dbadc38b10cdf1a2217d7c/merged
overlay 233G 199G 22G 91%
/var/lib/docker/overlay2/25e12dfd80f5f07d03b8fdf9d9e25321353e6743ab7011ac7120864f943c3fff/merged
overlay 233G 199G 22G 91%
/var/lib/docker/overlay2/c9e1ca07850113ceb3390ec1482ca5f890b0e992247869df64eebc113beed9f0/merged
overlay 233G 199G 22G 91%
/var/lib/docker/overlay2/0f73d652f46400a7694fd637aa2daf9f69f2dec3d28058277aac2b475f0bb5c9/merged
overlay 233G 199G 22G 91%
/var/lib/docker/overlay2/46a4bdb608b14efdf2ef85bc2fd59d769d8f72e1b9742e9edb97d33934cf6a34/merged
overlay 233G 199G 22G 91%
/var/lib/docker/overlay2/7489f202b103c981e87409622181ecd9749b0f6e891c4fe83bd5cf1db56d4ebd/merged
overlay 233G 199G 22G 91%
/var/lib/docker/overlay2/3a364eb74f496cdc9e323e20fbcb9f5742e2a0a298166b61cb2fe11e5d52e83c/merged
Not sure what these meant I've went to the next logical step: Google it!
Actually, duckduckgo to the help! Some quick research showed: The issue seems to vary in the version noted in the URL as well as in the endpoint/path:
error during connect: Post http://docker:2375/v1.39/auth: dial tcp: lookup docker on x.x.x.x:53: no such host
or for info:
ERROR: error during connect: Get http://docker:2375/v1.40/info: dial tcp: lookup docker on 192.168.65.1:53: no such host
Possible Solutions #
Ben Gift added an alias to the docker-compose.yml:
services:
- name: your_docker_image_location/docker:dind
alias: docker
Tucke shared in the same bug report another solution. He seemed to have solved it by editing the config.toml and adding "/var/run/docker.sock:/var/run/docker.sock" to the cache volume:
[[runners]]
...
[runners.docker]
volumes = ["/cache", "/var/run/docker.sock:/var/run/docker.sock"]
...
Patrice added privileged on top in this issue:
privileged = true
volumes = ["/cache","/var/run/docker.sock:/var/run/docker.sock"]
A deleted GitHub user had to open a port?
Maybe, but this is rather unlikely for me as similar commands worked on my elementary/Debian machine.
In the end, none of these solutions solved my issue. A coffee break later, my solution arrived: I restarted my laptop and the issue was resolved afterward.
🙏🙏🙏
Since you've made it this far, sharing this article on your favorite social media network would be highly appreciated 💖! For feedback, please ping me on Twitter.
Published