New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hash sum mismatch #23203
Comments
Appears to be related to #23202. |
Same problem on Debian Trusty
|
Similar problem on Travis CI with Ubuntu package. It was working an hour ago. https://travis-ci.org/goalgorilla/drupal_social/builds/134719276
|
Same on Debian Jessie: |
Can easily be repoduced in a contatiner also:
|
What about |
@Vanuan No, already tried. |
USER POLL The best way to get notified of updates is to use the Subscribe button on this page. Please don't use "+1" or "I have this too" comments on issues. We automatically The people listed below have upvoted this issue by leaving a +1 comment: @ViGo5190 |
Same here!
|
Things we've tried so far: Re-add the GPG key Blow the lists cache Apt clean None of them have resolved the issue |
Tried to install via apt. Checksum mismatch with the following file:
Tried the following procedures which did not help:
|
Maybe this would help |
Release contains: InRelease contains: the latter has been updated today, Date: Thu, 02 Jun 2016 11:06:54 UTC |
Running
|
Relevant output of
|
https://travis-ci.org/goalgorilla/drupal_social/builds/134730044
|
I get on Ubuntu Wily 15.10
I got the same before on Ubuntu Xenial 16.04. Is docker even added to the Xenial repo yet? |
Relevant output of
|
can we agree upon the fact that the hashsums are incorrect/repo needs administrative action? |
I worked around this by downloading the new package manually and installing using
|
Unfortunately dpkg installation doesn't seem to play well on Travis. |
Also, this is what happens to me when manually installing on Debian Stretch, using
Update: As I somehow expected, this was an unrelated problem. I fixed it by running |
ping @mlaventure @tiborvass PTAL! |
ETA? |
yes we need an ETA too, it's pretty urgent - our complete travis build chain is dead now -.- |
Here are the relevant files for xenial,
We can see that these files have been regenerated earlier today. In the Among the several causes for |
@simos So this should work on Xenial now? I thought docker still did not work on Xenial and we had to go back to Wily. (then again, I am an Ubuntu user since today so what do I know) |
@bmoorthamers You can manually check which repositories have mismatched hashes. See my post above. At least |
@vadviktor Does not work at Docker nor maintain the project. |
It appears to be working for Ubuntu Xenial now. |
FYI, this issue is on HN https://news.ycombinator.com/item?id=11822562 |
Trusty appears to be back up |
Hi everyone. I work at Docker. First, my apologies for the outage. I consider our package infrastructure as critical infrastructure, both for the free and commercial versions of Docker. It's true that we offer better support for the commercial version (it's one if its features), but that should not apply to fundamental things like being able to download your packages. The team is working on the issue and will continue to give updates here. We are taking this seriously. Some of you pointed out that the response time and use of communication channels seem inadequate, for example the @dockerststus bot has not mentioned the issue when it was detected. I share the opinion but I don't know the full story yet; the post-mortem will tell us for sure what went wrong. At the moment the team is focusing on fixing the issue and I don't want to distract them from that. Once the post-mortem identifies what went wrong, we will take appropriate corrective action. I suspect part of it will be better coordination between core engineers and infrastructure engineers (2 distinct groups within Docker). Thanks and sorry again for the inconvenience. |
heh - got the catalog but the package is missing - guess I'll have another cofee :-) |
I'm sad that my deer picture got less +1s than the official answer. |
I have already installed docker with https://get.docker.com | sh without any error. |
We localized the cause of the issue, and if should be resolved now, please try again. It may be needed to clear the apt-cache;
|
Thanks for the fix @thaJeztah |
Well, that was quick for an unexpected issue, thanks. |
@snario you're welcome; can't take credit for the fix, but happy to see it's been sorted out 😅 |
👍 |
Sadly with this on the top of hacker news there's going to be billions of comments. Big thanks for the quick fix @thaJeztah. I wonder if we should lock this thread before they show up. |
Up until now there have been A As posted earlier, you can use a script to get an audio notification as soon as the main docker repositories are fixed, |
@simos see my earlier comment; #23203 (comment) the issue should be resolved |
@thaJeztah I verified that the issue has been resolved. Tested on Ubuntu 15.10. Thanks to all the other Docker folks that helped resolve this issue quickly. |
Thank you all for the reports: we're very sorry for this. We're looking into the details and the timeline of events that lead to this, and we'll make sure it doesn't happen again. I'm closing the issue, but of course feel free to let me know if you see any remaining quirks. |
Ubuntu 14.04 Here, issue solved ! |
Probably shouldn't be surprised, but it is shocking how many people risk their infrastructure with hard dependencies on external repos. I don't even do that with my home systems. And then complain about Docker having a single point of failure? |
@jalawrence Docker is the tip of the iceberg... |
Steps to reproduce the issue:
apt-get update
Describe the results you received:
Running
apt-get update
on Debian Stretch just now results inas well as
I have cleaned the apt caches and tried again with the same result. Also, I'm not using a proxy.
Describe the results you expected:
No error.
The text was updated successfully, but these errors were encountered: