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

I/O timeout on upgrade #1937

Closed
ain opened this Issue Oct 5, 2015 · 5 comments

Comments

Projects
None yet
2 participants
@ain

ain commented Oct 5, 2015

Following the ideas from the issue of moby/moby#16746, running

    docker-machine upgrade <machine>

fails with

$ docker-machine upgrade dev
Stopping machine to do the upgrade...
Upgrading machine dev...
Get https://api.github.com/repos/boot2docker/boot2docker/releases: dial tcp: i/o timeout

The platform is OS X El Capitan with

$ docker version
Client:
 Version:      1.8.2
 API version:  1.20
 Go version:   go1.4.2
 Git commit:   0a8c2e3
 Built:        Thu Sep 10 19:10:10 UTC 2015
 OS/Arch:      darwin/amd64

Server:
 Version:      1.8.1
 API version:  1.20
 Go version:   go1.4.2
 Git commit:   d12ea79
 Built:        Thu Aug 13 02:49:29 UTC 2015
 OS/Arch:      linux/amd64
@nathanleclaire

This comment has been minimized.

Contributor

nathanleclaire commented Oct 6, 2015

I've got a fix for this in the pipe

@nathanleclaire

This comment has been minimized.

Contributor

nathanleclaire commented Oct 6, 2015

Hm, actually, it seems I have mis-read this issue and I'm thinking of a different one. Do subsequent docker-machine upgrade commands work, or do you get the same error? How about restarting the VM, does it fix the issue?

@ain

This comment has been minimized.

ain commented Oct 6, 2015

No to all questions, unfortunately. Tried multiple times. On a different machine that still runs 1.8.1, the error is slightly different:

    $ docker-machine upgrade dev
    Stopping machine to do the upgrade...
    exit status 1
@ain

This comment has been minimized.

ain commented Oct 14, 2015

Problem resolved by swopping Google DNS so that 8.8.8.8 became primary and 4.4.4.4 secondary DNS server. May have been DNS cache issue.

@ain ain closed this Oct 14, 2015

@nathanleclaire

This comment has been minimized.

Contributor

nathanleclaire commented Oct 14, 2015

Thanks for following up to close @ain

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment