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
docker login fails while docker-compose is installed on Ubuntu 18.04 #6023
Comments
Looks like a bug with the Ubuntu package, which is not owned by us. Additionally, the version the package installs (1.17.1) is no longer supported. Please follow the official install instructions instead: https://docs.docker.com/compose/install/ |
adding that: following the official install instructions does not work when working on ARM platform (RPi)
which can't find anything when it's apart of the cURL command to download the latest :/ any word on if/when ARM boards might be supported directly? |
I'm having the same issue woth Ubuntu18.04 server. I have tried with
but I keep getting Installed packages version: $ docker --version |
@tuddman We don't provide a build for arm architectures, but you can install the latest version using @lucafallabrino That's a completely unrelated issue. You're trying to use the secretservice credential helper on a server without X11, which isn't going to work. Use |
I'm having the same (or a similar) issue, running |
hi, why is the issue closed? the workaround from @kiliankoe works but it is still a problem on a new ubuntu 18.04 installation. |
Closed because not a Compose issue: #6023 (comment) |
It's very much an issue. Fresh install of 18.04, installed docker-compose through pip. Exact same issue. |
I found that if you remove the golang-docker-credential-helpers package after switching to docker-ce and not the bundled docker package in ubuntu 18.04, this problem is resolved. |
Since this is a bug in the Ubuntu packaging for server it needs to be fixed there but in the meantime a work-around without having to uninstall docker-compose temporarily or having to switch to the docker repos instead you can make it use
This generates a you a gpg2 key, After that's done you can list it with
Copy the key id (from the line labelled
After that Side effect is that you get a somewhat more secure credentials store or on your server instead of a base64 encoded json file. |
This happened to me on freshly installed @prg3 solution (which is running |
I added a bug report here, https://bugs.launchpad.net/ubuntu/+source/golang-github-docker-docker-credential-helpers/+bug/1794307 |
@jessehallam can you please try this package instead?
This is version we ship and support with Canonical Kubernetes and I've never had any issue logging into registries with this agent (From the kubernetes 1.11 release notes):
Also, @tuddman we do ship and support Docker on ARM as we actually support Kubernetes on ARM today. There are big differences in ARM architectures, but you might also want to try the package above. If it is missing, I might be able to help with that:
|
@CalvinHartwell We've run into this with both the official Ubuntu |
Seems related with user profile : |
Hi, @CalvinHartwell same issue with docker.io |
I confirm that I'm hitting the same freshly provisioned systems where in installed docker.io and docker-compose in one shot: Does anyone have a workaround? I didn't have the package installed for the |
@afalko you can use sudo su - and docker login right after |
Of course this is just a workaround, use a full root access is not a good idea |
Thanks @fredbcode ! I wound up automating this with the following workaround:
|
I have the issue as well |
Deleting docker-compose (apt-get autoremove) is the workaround |
@trebonius0 you made exactly |
yes |
removing golang will remove bunch of python stuff and docker-compose. |
Follow @shin-'s advice:
don't do |
I think I followed chriswue's advice and did gpg2 generating the key and then used the pass to set the credentials and was able to docker login |
If all else fails (@shin-'s advice didn't help me), you can always generate a ~/.docker/config.json with the creds baked in. |
Another tip for those who use Ansible in their CI, the docker_login module helped me out too. |
This docker/docker-credential-helpers#105 (comment) worked for me |
At the very least, a better error message from docker login would be useful... just wasted half an hour on a goose chase around X11 Display... where a better message could've pointed straight towards using gnupg2 pass |
I disagree, not a better message, when x11 is not installed we should use docker login without any error. |
Exactly this. This behavior makes zero sense. |
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910822 |
|
Again, this is a very poor solution. It is a workaround at best, and not a good one. I wish there was more involvement by maintainers. |
Please, for those of you participating in this thread, go vote for https://bugs.launchpad.net/ubuntu/+source/docker-compose/+bug/1796119 and mark it as affecting you, or it will never get fixed. |
I'm seeing this issue even when following the official instructions to install docker-compose (https://docs.docker.com/compose/install/#install-compose)
Same problem is I move to:
As a side note, this issue is compounded by the fact the Ubuntu packages and the "official" docker packages are disjointed. You have the docker.io packages on Ubuntu vs. the docker-ce packages from the official download. Seems to make things that more confusing as it's not obvious which combination of packages one needs, especially when running into issues such as the above. |
Honestly, I have no idea what docker devs are thinking. I think at this point closing this bug was a huge mistake; docker, docker-compose, and the various distro devs need to actually work together and not just point fingers at each other. |
Bug reports have been filed on the Ubuntu and Debian trackers. As explained throughout the thread, this issue is unrelated to Compose. You can uninstall the problematic package ( |
Description of the issue
This error appears on a fresh Ubuntu Server 18.04 install. It has virtually nothing installed except docker and docker-compose. This error only occurs when docker-compose is installed.
Typing
sudo apt remove docker-compose
clears the error. Login now occurs using the normal docker prompt.Context information (for bug reports)
docker-compose version 1.17.1, build unknown
docker-py version: 2.5.1
CPython version: 2.7.15rc1
OpenSSL version: OpenSSL 1.1.0g 2 Nov 2017
Client:
Version: 17.12.1-ce
API version: 1.35
Go version: go1.10.1
Git commit: 7390fc6
Built: Wed Apr 18 01:23:11 2018
OS/Arch: linux/amd64
Server:
Engine:
Version: 17.12.1-ce
API version: 1.35 (minimum version 1.12)
Go version: go1.10.1
Git commit: 7390fc6
Built: Wed Feb 28 17:46:05 2018
OS/Arch: linux/amd64
Experimental: false
ubuntu@:~$ docker-compose config
ERROR:
Can't find a suitable configuration file in this directory or any
parent. Are you in the right directory?
Steps to reproduce the issue
sudo apt install docker
sudo apt install docker-compose
docker login
Observed result
Expected result
The normal docker login prompt.
Stacktrace / full error message
Additional information
OS version / distribution,
docker-compose
install method, etc.This machine was built using Amazon AWS's Canonical Ubuntu 18.04 AMI. It has virtually nothing installed on it, except for docker, docker-compose and sshd.
The text was updated successfully, but these errors were encountered: