Bug 1529359

Summary:	Private repository: docker push works, but pull fails with Authentication failure
Product:	[Fedora] Fedora	Reporter:	Raman Gupta <rocketraman>
Component:	docker	Assignee:	Antonio Murdaca <amurdaca>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	30	CC:	adimania, admiller, amurdaca, dwalsh, ichavero, jcajka, lsm5, marianne, nalin, santiago
Target Milestone:	---	Keywords:	Reopened
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:	Feature: Docker daemon flag --signature-verification=false Reason: The lack of this flag causes problems with pulling from most current registries. Result: If this flag is missing (which it was by default for a while) the user will have issues pulling from most registries. Even though the default appears to have been fixed (see https://bugzilla.redhat.com/show_bug.cgi?id=1502560), I believe this flag should still be documented in Fedora's documentation.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-05-26 14:36:06 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Raman Gupta 2017-12-27 19:56:04 UTC

Description of problem:

I am able to push to a private registry, but when attempting to pull, I get an 'unauthorized: authentication required' error. This used to work fine. It also works fine with the same private registry using Docker 1.13.1 on Ubuntu, so it does not appear to be a problem with the registry itself.

Reproduction recipe:

$ docker run -it hello-world
[...]
$ docker tag hello-world myregistry/hello-world
$ docker push myregistry/hello-world
The push refers to a repository [myregistry/hello-world]
f999ae22f308: Pushed 
latest: digest: sha256:8072a54ebb3bc136150e2f2860f00a7bf45f13eeb917cca2430fcd0054c8e51b size: 524
$ docker pull myregistry/hello-world
Using default tag: latest
Trying to pull repository myregistry/hello-world ... 
unauthorized: authentication required


Version-Release number of selected component (if applicable):

docker-1.13.1-44.git584d391.fc26.x86_64


How reproducible:

Every time

Comment 1 Daniel Walsh 2017-12-30 10:50:49 UTC

Antonio is this caused by us reversing the registries?

Comment 2 Fedora End Of Life 2018-05-03 07:55:28 UTC

This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '26'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 26 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 3 Fedora End Of Life 2018-05-29 12:16:38 UTC

Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26
is no longer maintained, which means that it will not receive any
further security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 4 Raman Gupta 2018-09-17 19:52:49 UTC

This is still happening on Fedora 27.

Comment 5 Raman Gupta 2018-09-17 22:39:37 UTC

Hmm, looks like the error message was just very imprecise, and that there is some flag I found here `https://bugzilla.redhat.com/show_bug.cgi?id=1502560` which is not documented anywhere, which needs to be set to false, at least for the registry I am connecting to (an Azure-managed container registry).

So, adding `--signature-verification=false` to /etc/sysconfig/docker OPTIONS solves the problem.

If this `--signature-verification` flag is something Redhat-specific (and it seems to be, given I can't find any documentation about it anywhere), then it definitely needs some documentation somewhere, and better error handling.

Comment 6 Ben Cotton 2018-11-27 14:39:41 UTC

This message is a reminder that Fedora 27 is nearing its end of life.
On 2018-Nov-30  Fedora will stop maintaining and issuing updates for
Fedora 27. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora  'version' of '27'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 27 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 7 Ben Cotton 2019-02-19 17:11:26 UTC

This bug appears to have been reported against 'rawhide' during the Fedora 30 development cycle.
Changing version to '30.

Comment 8 Ben Cotton 2020-04-30 22:10:14 UTC

This message is a reminder that Fedora 30 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '30'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 30 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 9 Ben Cotton 2020-05-26 14:36:06 UTC

Fedora 30 changed to end-of-life (EOL) status on 2020-05-26. Fedora 30 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.