`docker login; docker push` fails
gracebrownecodes opened this issue · 5 comments
Even after logging in, the docker push command tries to get authentication details interactively. Passing the details as a heredoc fails with a docker error about invalid ioctl. I believe this may be related to a breaking change in the docker hub auth API in version 1.7. Where does Circle CI stand on installing an updated docker version? My attempts to script it in my circle.yml have failed miserably...
Yeah - the containers by default run old Docker - we plan to update our containers with the latest Docker. For the time-being, can you try using the following commands to upgrade Docker (also please remove docker from machine.services):
machine:
pre:
- |
sudo curl -L -o /usr/bin/docker 'http://s3-external-1.amazonaws.com/circle-downloads/docker-1.6.2-circleci'
sudo chmod 0755 /usr/bin/docker
sudo start docker
Let me know how it goes!
Yeah, I've got that version running in my Circle CI instances using the below circle.yml sections (found the previous ticket). Unfortunately, I'm still running into the same problem. I think there may have been some breaking changes in authentication with Docker Hub in the 1.7 release. Any idea of the timeline for docker 1.7 in the Circle CI environment? Any other suggestions?
machine:
services:
- docker
dependencies:
pre:
- sudo service docker stop && sudo curl -L -o /usr/bin/docker
'http://s3-external-1.amazonaws.com/circle-downloads/docker-1.6.2-circleci'
&& sudo chmod 0755 /usr/bin/docker && sudo service docker start
Can you remove docker from machine.services section? I believe that should fix the problem.
We are working on supporting Docker 1.7 - should be coming relatively soon.
I'm getting the same problem even after removing docker from machine.services. Can you reproduce on a Circle CI instance where you believe it should work? The steps are simple, docker login followed by docker push.
I have reproduced the process with 1.6.2 here: https://circleci.com/gh/circleci/docker-elasticsearch/55 based on [1]. May I suggest reaching CircleCI support - our support engineers can dig into your build better and debug the issue.