-
Notifications
You must be signed in to change notification settings - Fork 528
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
Repository down #155
Comments
It seems like the domain is expired... |
what's going on? 8 hours already |
Indexes used by apk in Instead of See options. |
I had the same issue, it seems fixed now. |
The alpinelinux.org domain expired and was renewed. It is taking a while for caches to expire and get the correct IP addresses again. It should start working again today. |
I am having this problem now |
I'm also seeing it all of a sudden today. Can't resolve |
@andyshinn I'm seeing that it's still registered, but there's no nameservers for |
should be back now |
If I see that correctly, the domain cannot be resolved because the name server hostnames rely on it. Name Server: NS2.ALPINELINUX.ORG |
glue records are used to solve that problem. |
@ncopa you're right. |
Still getting this |
@Niktrix exactly what are you getting? IO error? DNS lookup failure? something else? |
ERROR: http://dl-cdn.alpinelinux.org/alpine/v3.4/main: temporary error (try again later) |
I'm getting this today whenever I try to
|
@nihakue Try restarting Docker, that solved it for me today. |
I've been having a similar issue.
I can access dl-cdn.alpinelinux.org and dl-4.alpinelinux.org. I can use wget on the host to download APKINDEX.tar.gz files. Tried restarting the docker service and restarting the host vm (centos 6), neither of those seemed to help. Not really sure where to go from here. |
Use this: # Use dl-4, as the main repo is down (23.08.2016)
RUN sed -i -e 's/dl-cdn/dl-4/' /etc/apk/repositories && \
apk add --no-cache \
bash \
build-base \
... |
The @IlyaSemenov solution works for me. Thanks |
@IlyaSemenov Thanks!! RUN apk add --no-cache nodejs || \
(sed -i -e 's/dl-cdn/dl-4/g' /etc/apk/repositories && apk add --no-cache nodejs) |
Well, I retried and it works like |
running into this again.
|
repository down?
|
Build fails on hub.docker.com too.
|
This fixed it for me...
I'm following Victor Farcic's DevOps 2.1 tutorial / book. |
Seems to be resolved. |
I got the error again today. Has anyone encountered this again ? |
@danielmihai Try restarting Docker, that solved it for me today. |
I did that 3 times already, even replaced the dl-cdn with dl-4.. doesn't
work.. any other recommendations ?
Important detail: i'm behind a proxy. i've set the docker proxy options as
recommended in the docker docs.
…On Mon, Apr 24, 2017 at 5:10 PM, alamzeeshan ***@***.***> wrote:
@danielmihai <https://github.com/danielmihai> Try restarting Docker, that
solved it for me today.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#155 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABzKA2qXAO_KeHeU8JPJOeAYWSDr5kkpks5rzK1bgaJpZM4H2yQE>
.
|
@danielmihai Did you check that the packages you're trying to install are actually in those repositories? I've just had an issue where one of the packages moved to /edge/community repository and another one moved to /v3.5/main |
@danielmihai were you able to resolve this issue? |
Haven't tried again, had to finish the task, so I found a workaround,
didn't need those images for the task.. will try again after I finish with
all.
Thanks for supporting me!
…On Wed, Apr 26, 2017 at 12:27 PM, Katiyman ***@***.***> wrote:
@danielmihai <https://github.com/danielmihai> were you able to resolve
this issue?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#155 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABzKA32lVU4KsVGuLxlyTbhJn2peVRB_ks5rzw3sgaJpZM4H2yQE>
.
|
Add Google's DNS to your nameservers list
|
Domain alpinelinux.org is down again. Anyone else? |
Yes it down for me as well |
I'm facing the same problem, any idea? |
Down again today - 503 on http://dl-cdn.alpinelinux.org/alpine/v3.4/main/x86_64/APKINDEX.tar.gz |
for me as well:
|
So kinda hacky, but if you want to be unblocked, figure out the version you need and add the mirror like so (Dockerfile): Then you can run your apk commands: There are other mirror sites, 1-5: But at this moment I am only able to get dl-5 working. Hope this helps anyone! @stephanlindauer Or alternatively, you can pass as argument: |
This has been down for me a lot since Friday (5/12). When I am seeing the issue, adding the dl-1, dl-2, etc mirrors does not help. |
dl-1 looks to be down atm. |
Looks like they gave up on using tls on the dl-[1-5].alpinelinux.org servers? |
Looks like https://dl-3.alpinelinux.org/ is working currently, combine that with @camsjams suggestion and you can properly get TLS for production. Worked in my case |
Oh wow, thanks. I didn't think to try all of them. dl-3 and only dl-3 has a legit cert. Thanks! I'm doing this for good measure:
|
@erkolson seems your solution didn't help me. |
After some debugging and googling I found that problem was inside the container and based on DNS, so the best way in my case was: Link to - http://stackoverflow.com/a/42332682 |
This specific issue "Repository down" with IO ERROR form March 2016 was resolved in March 2016. Please open new issue if you have new issues. |
I'm using this image but as soon as I start using the command
RUN apk update && apk upgrade
it throws errors on missing repositories:
`fetch http://dl-cdn.alpinelinux.org/alpine/v3.3/main/x86_64/APKINDEX.tar.gz
ERROR: http://dl-cdn.alpinelinux.org/alpine/v3.3/main: IO ERROR
WARNING: Ignoring APKINDEX.5a59b88b.tar.gz: No such file or directory
fetch http://dl-cdn.alpinelinux.org/alpine/v3.3/community/x86_64/APKINDEX.tar.gz
ERROR: http://dl-cdn.alpinelinux.org/alpine/v3.3/community: IO ERROR
WARNING: Ignoring APKINDEX.7c1f02d6.tar.gz: No such file or directory
2 errors; 11 distinct packages available
`
It looks like the content delivery network is down or it changed
The text was updated successfully, but these errors were encountered: