Tecnativa / Tecnativa/docker-socket-proxy

Error accessing proxy from traefik

Open
#94 6 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
2.8k
Forks
207
PR merge metrics
No merged PRs in 30d

Description

I'm using this with traefik and it works like a charm.

...Except when it doesn't. For example, when I must update services, and then restart traefik. Then traefik restarts without error, and the container becomes "healthy". But requests to services time out.

I thought it was a traefik problem. Then I checked the logs, and every time I have this issue I see something like this:

time="2023-07-17T07:44:45+03:00" level=error msg="Provider connection error error during connect: Get "http://tecnativa:2375/v1.24/version": dial tcp: lookup tecnativa on 127.0.0.11:53: no
such host, retrying in 9.503388201s" providerName=docker

The "no such host" part is incorrect, because the tecnativa container is working, and reported as "healthy". I wonder what that v1.24 is?

The only solution is to restart both traefik and tecnativa (and sometimes other services which are served by traefik!)

I am using the most recent official tecnativa release 0.1.1. And docker 24.0.4 on debian.

Any ideas?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source file or test is named. Start by reproducing the restart sequence with docker-socket-proxy 0.1.1, Docker 24.0.4 on Debian, and Traefik, then compare the proxy and Traefik logs around the DNS failure. Done means identifying the cause of the failed service lookup and defining a verified fix or documented workaround.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker
Domain
infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.