Docker Debian apt Error Reading from Server

后端 未结 5 2013
迷失自我 2021-02-20 18:26

It would seem that apt-get is having issues connecting with the repository servers. I suppose it is likely compatibility issues, as mentioned here, however the proposed solution

  • 2021-02-20 18:38

    For whoever is having an issue with this, this is my attempt to "fix" the issue by swapping out httpredir with a single working domain whenever the Dockerfile is being built:

    FROM debian:je...
    # Insert this line before "RUN apt-get update" to dynamically
    # replace with a single working domain
    # in attempt to "prevent" the "Error reading from server" error.
    RUN sed -i "s/`curl -s -D - | awk '/^Link:/ { print $2 }' | sed -e 's@<http://\(.*\)/debian/>;@\1@g'`/" /etc/apt/sources.list
    # Continue with your apt-get update...
    RUN apt-get update...

    What this command does is:

    1. Curl the from the building machine to get the headers from debian demo page (-s is silent, don't output. -D is to dump headers)
    2. Extract the headers, find the Link header fragment. This contains the best route as recommended by httpredir.
    3. The last sed -e ... is to extract out the domain name of the link in step 2.
    4. Then finally, the domain found in step 3 is being feed into the global sed command, and replace the domain found in /etc/apt/sources.list.

    This is not a fix, but rather a simple hack to (greatly) reduce the chances of failed build. And... pardon me if it looks weird, as it's my virgin sed & piping attempt.


    On a side note, if the domain that it picks simply too slow or not responding as it should, you may want to do it manually by

    1. Visit, and you should see a link there like http://......./debian/. For example, at the point of writing, I saw

    2. Instead of the long RUN sed -i.... command, use this instead:

      RUN sed -i "s/" /etc/apt/sources.list
    0 讨论(0)
  • 2021-02-20 18:41

    The mirror is "magic" in that it will load-balance and geo-ip you to transparent increase performance and availability. I would therefore immediately suspect it of causing your problem, or at least be the first thing to rule out.

    I would check if you could:

    • Still reproduce the problem; will throw out "bad" mirrors from its internal lists so your issue may have been temporary.

    • Reproduce the problem with a different, mirror. Try something like If it then works with this mirror, do please contact the maintainer and report the issue to them. They are quite responsive and open to bug reports.

    0 讨论(0)
  • 2021-02-20 18:46

    For those visiting with similar issues, using the --no-cache flag in the docker build may help. Similar issues (though not this exact one) can occur if the apt-get update is old and not being recalled sue to caching.

    0 讨论(0)
  • 2021-02-20 18:47

    Not enough reputation to comment on previous answers, so I will (confusingly) add a new answer:

    • I don't think hardcoding a single mirror is really a viable solution, since as for example seen here, there's a reason debian implemented the whole httpredir thing -- mirrors go down or out of date.
    • I've dealt with this issue a lot of times, and the logs always indicate that docker's actually running the apt-get command, which means --no-cache is unlikely to be fixing it -- it's just that if you rebuild, httpredir is likely to pick a different mirror, even if you don't change anything in your docker file, and the build will work.
    0 讨论(0)
  • 2021-02-20 18:59

    I added apt-get clean to my dockerfile before the apt-get update line, it seems to have done the trick.

    I guess I have no way of knowing whether or not it was the extra command or if it was luck that fixed my build, but I took the advice from

    0 讨论(0)