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
apt.dockerproject.org not availible from ipv6-only host #18342
Comments
Possibly related to #17790 /cc @jfrazelle ? |
yes closing as dup of that |
Thanks @jfrazelle I wasn't sure if it was on the same infrastructure 😄 |
Cool! |
For me it doesn't work. I tried the DNS of my ISP and the resolver from Google. |
I had to turn it off because it broke something, looking at another way On Mon, Jan 25, 2016 at 2:54 PM, Thomas Schäfer notifications@github.com
|
Are the any news on this issue? |
It was SSL with gnu tls on the cloud flare ipv6 proxy that broke, it's all
documented in this issue if you read the thread...
…On Apr 1, 2017 12:55, "Andreas Rammhold" ***@***.***> wrote:
Are the any news on this issue?
@jessfraz <https://github.com/jessfraz> what did break when you did
enable IPv6?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#18342 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABYNbKehGc8A4NDJSPEMHgOqvFaxvYvvks5rri0OgaJpZM4Gsior>
.
|
[ Duplicating post https://github.com//issues/17790#issuecomment-364378339 since this issue (#17790) was about get.docker.com and not apt.dockerproject.org which is used as Debian Docker repository and which is still IPv4-only ] Hi, do you think it might be possible to try to enable IPv6 support again? Some other projects also using deb apt to access Amazon CloudFront hosted repositories with IPv6 + TLS seem to have it working for one year now: nodesource/distributions#170 (deb.nodesource.com). Amazon indeed introduced IPv6 support in CloudFront in October 2016: https://aws.amazon.com/about-aws/whats-new/2016/10/ipv6-support-for-cloudfront-waf-and-s3-transfer-acceleration/ . [ P.S.: as per indicated in https://github.com//issues/17790#issuecomment-365105419 IPv6 has already been successfully enabled for download.docker.com, get.docker.com and test.docker.com, but not yet apt.dockerproject.org ] |
@slugan (copying here as well) apt.dockerproject.org is deprecated, and only kept for legacy releases; all current releases are published to https://download.docker.com (which contains both the apt and yum repositories, as well as static builds) |
Thanks for the info @thaJeztah! Here is the process I followed to switch to the new repository on Jessy:
Everything is indeed working perfectly with IPv6-only connectivity. Thanks again! |
It's currently not possible to install docker on an debian machine that's ipv6-only:
$ host -t AAAA apt.dockerproject.org
apt.dockerproject.org is an alias for j.global-ssl.fastly.net.
$ host -t AAAA j.global-ssl.fastly.net.
j.global-ssl.fastly.net has no AAAA record
Could you please add a AAAA record so that you can install docker on ipv6-only hosts.
BUG REPORT INFORMATION
Use the commands below to provide key information from your environment:
docker version: 1.9
docker info: N/A
uname -a: Linux geordi 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt11-1+deb8u6 (2015-11-09) x86_64 GNU/Linux
Provide additional environment details (AWS, VirtualBox, physical, etc.):
List the steps to reproduce the issue:
Describe the results you received:
W: Failed to fetch https://apt.dockerproject.org/repo/dists/debian-jessie/main/binary-amd64/Packages
E: Some index files failed to download. They have been ignored, or old ones used instead.
Describe the results you expected:
able to install docker
Provide additional info you think is important:
----------END REPORT ---------
The text was updated successfully, but these errors were encountered: