Upgrading to machine 0.5.4 can not connect to existing docker containers on AWS

[sjwhyte]

I upgraded to docker-machine 0.5.4 after the upgrade I upgraded my default local docker instance, but when I go and list all of my instance, which are mostly on AWS I get the following:

AME           ACTIVE   DRIVER      STATE   URL   SWARM   DOCKER    ERRORS
da-backend-1   -        amazonec2   Error                 Unknown   Problem with AWS API call: Non-200 API response: code=401 message=Authorization header or parameters are not formatted correctly.

da-web-1   -    amazonec2   Error             Unknown   Problem with AWS API call: Non-200 API response: code=401 message=Authorization header or parameters are not formatted correctly.

default        -    virtualbox   Stopped             Unknown
demo-backend   -    amazonec2    Error               Unknown   Problem with AWS API call: Non-200 API response: code=401 message=Authorization header or parameters are not formatted correctly.

demo-web-1   -    amazonec2   Error             Unknown   Problem with AWS API call: Non-200 API response: code=401 message=Authorization header or parameters are not formatted correctly.

demo-web-2   -    amazonec2   Error             Unknown   Problem with AWS API call: Non-200 API response: code=401 message=Authorization header or parameters are not formatted correctly.

development-backend   -    amazonec2   Error             Unknown   Problem with AWS API call: Non-200 API response: code=401 message=Authorization header or parameters are not formatted correctly.

development-web-1   -    amazonec2   Error             Unknown   Problem with AWS API call: Non-200 API response: code=401 message=Authorization header or parameters are not formatted correctly.

production-backend-1   -    amazonec2   Error             Unknown   Problem with AWS API call: Non-200 API response: code=401 message=Authorization header or parameters are not formatted correctly.

production-web-1   -    amazonec2   Error             Unknown   Problem with AWS API call: Non-200 API response: code=401 message=Authorization header or parameters are not formatted correctly.

production-web-2   -    amazonec2   Error             Unknown   Problem with AWS API call: Non-200 API response: code=401 message=Authorization header or parameters are not formatted correctly.

qa-backend-1   -    amazonec2   Error             Unknown   Problem with AWS API call: Non-200 API response: code=401 message=Authorization header or parameters are not formatted correctly.

qa-web-1   -    amazonec2   Error             Unknown   Problem with AWS API call: Non-200 API response: code=401 message=Authorization header or parameters are not formatted correctly.

staging-backend-1   -    amazonec2   Error             Unknown   Problem with AWS API call: Non-200 API response: code=401 message=Authorization header or parameters are not formatted correctly.

staging-web-1   -    amazonec2   Error             Unknown   Problem with AWS API call: Non-200 API response: code=401 message=Authorization header or parameters are not formatted correctly.

I reverted to 0.5.0 (the version that was on before, toolbox 1.9.0) and everything reported fine:

NAME                   ACTIVE   DRIVER       STATE     URL                         SWARM
da-backend-1           -        amazonec2    Running   tcp://xx.xx.xx.xx:2376
da-web-1               -        amazonec2    Running   tcp://xx.xx.xx.xx:2376
default                -        virtualbox   Running   tcp://xx.xx.xx.xx:2376
demo-backend           -        amazonec2    Running   tcp://xx.xx.xx.xx:2376
demo-web-1             -        amazonec2    Running   tcp://xx.xx.xx.xx:2376
demo-web-2             -        amazonec2    Running   tcp://xx.xx.xx.xx:2376
development-backend    -        amazonec2    Running   tcp://xx.xx.xx.xx:2376
development-web-1      -        amazonec2    Running   tcp://xx.xx.xx.xx:2376
production-backend-1   -        amazonec2    Running   tcp://xx.xx.xx.xx:2376
production-web-1       -        amazonec2    Running   tcp://xx.xx.xx.xx:2376
production-web-2       -        amazonec2    Running   tcp://xx.xx.xx.xx:2376
qa-backend-1           -        amazonec2    Running   tcp://xx.xx.xx.xx:2376
qa-web-1               -        amazonec2    Running   tcp://xx.xx.xx.xx:2376
staging-backend-1      -        amazonec2    Running   tcp://xx.xx.xx.xx:2376
staging-web-1          -        amazonec2    Running   tcp://xx.xx.xx.xx:2376

I then decided to upgrade to 0.5.5 and now I get the following:

NAME                   ACTIVE   DRIVER       STATE     URL   SWARM   DOCKER    ERRORS
da-backend-1           -        amazonec2    Error                   Unknown   EmptyStaticCreds: static credentials are empty
da-web-1               -        amazonec2    Error                   Unknown   EmptyStaticCreds: static credentials are empty
default                -        virtualbox   Stopped                 Unknown
demo-backend           -        amazonec2    Error                   Unknown   EmptyStaticCreds: static credentials are empty
demo-web-1             -        amazonec2    Error                   Unknown   EmptyStaticCreds: static credentials are empty
demo-web-2             -        amazonec2    Error                   Unknown   EmptyStaticCreds: static credentials are empty
development-backend    -        amazonec2    Error                   Unknown   EmptyStaticCreds: static credentials are empty
development-web-1      -        amazonec2    Error                   Unknown   EmptyStaticCreds: static credentials are empty
production-backend-1   -        amazonec2    Error                   Unknown   EmptyStaticCreds: static credentials are empty
production-web-1       -        amazonec2    Error                   Unknown   EmptyStaticCreds: static credentials are empty
production-web-2       -        amazonec2    Error                   Unknown   EmptyStaticCreds: static credentials are empty
qa-backend-1           -        amazonec2    Error                   Unknown   EmptyStaticCreds: static credentials are empty
qa-web-1               -        amazonec2    Error                   Unknown   EmptyStaticCreds: static credentials are empty
staging-backend-1      -        amazonec2    Error                   Unknown   EmptyStaticCreds: static credentials are empty
staging-web-1          -        amazonec2    Error                   Unknown   EmptyStaticCreds: static credentials are empty

As for the local instance it seems to work fine after upgrading, but any AWS instance cause some issue depending on the version I upgrade to.

[jeanlaurent]

Could this be related to expired credentials like described in #1840

The ec2 driver has been quite changed since 0.5.4, would it be possible that you try out 0.5.6 ?

[Gogistics]

i got the same error after upgrading my docker-machine to 0.6.0

[mikus]

I confirm this error existence on docker-machine 0.6.0.