docker update errors with recently upgraded f27 system

[Robert P. J. Day]

  just did a full upgrade to fedora 27 a few days ago, first couple
updates worked fine, then this .. thoughts? should i just wait for
upstream to fix itself?


 Problem 1: cannot install the best update candidate for package
docker-2:1.13.1-26.gitb5e3294.fc27.x86_64
  - nothing provides atomic-registries >= 1.19.1-6 needed by
docker-2:1.13.1-42.git4402c09.fc27.x86_64
 Problem 2: package kubernetes-node-1.7.3-1.fc27.x86_64 requires docker, but none of the
providers can be installed
  - package docker-2:1.13.1-26.gitb5e3294.fc27.x86_64 requires docker-common =
2:1.13.1-26.gitb5e3294.fc27, but none of the providers can be installed
  - cannot install both docker-common-2:1.13.1-42.git4402c09.fc27.x86_64 and
docker-common-2:1.13.1-26.gitb5e3294.fc27.x86_64
  - cannot install both docker-common-2:1.13.1-26.gitb5e3294.fc27.x86_64 and
docker-common-2:1.13.1-42.git4402c09.fc27.x86_64
  - cannot install the best update candidate for package
kubernetes-node-1.7.3-1.fc27.x86_64
  - cannot install the best update candidate for package
docker-common-2:1.13.1-26.gitb5e3294.fc27.x86_64
  - nothing provides atomic-registries >= 1.19.1-6 needed by
docker-2:1.13.1-42.git4402c09.fc27.x86_64
 Problem 3: problem with installed package docker-2:1.13.1-26.gitb5e3294.fc27.x86_64
  - package docker-2:1.13.1-26.gitb5e3294.fc27.x86_64 requires docker-rhel-push-plugin =
2:1.13.1-26.gitb5e3294.fc27, but none of the providers can be installed
  - cannot install both docker-rhel-push-plugin-2:1.13.1-42.git4402c09.fc27.x86_64 and
docker-rhel-push-plugin-2:1.13.1-26.gitb5e3294.fc27.x86_64
  - cannot install both docker-rhel-push-plugin-2:1.13.1-26.gitb5e3294.fc27.x86_64 and
docker-rhel-push-plugin-2:1.13.1-42.git4402c09.fc27.x86_64
  - cannot install the best update candidate for package
docker-rhel-push-plugin-2:1.13.1-26.gitb5e3294.fc27.x86_64
  - nothing provides atomic-registries >= 1.19.1-6 needed by
docker-2:1.13.1-42.git4402c09.fc27.x86_64
================================================================================
 Package                  Arch    Version                        Repository
                                                                           Size
================================================================================
Skipping packages with conflicts:
(add '--best --allowerasing' to command line to force their upgrade):
 docker-common            x86_64  2:1.13.1-42.git4402c09.fc27    updates   85 k
 docker-rhel-push-plugin  x86_64  2:1.13.1-42.git4402c09.fc27    updates  1.7 M
Skipping packages with broken dependencies:
 docker                   x86_64  2:1.13.1-42.git4402c09.fc27    updates   20 M

Transaction Summary
================================================================================
Skip  3 Packages

Nothing to do.
Complete!

[Ed Greshko]

On 11/25/17 19:29, Robert P. J. Day wrote:
>    just did a full upgrade to fedora 27 a few days ago, first couple
>  updates worked fine, then this .. thoughts? should i just wait for
>  upstream to fix itself?
>
>
>   Problem 1: cannot install the best update candidate for package
> docker-2:1.13.1-26.gitb5e3294.fc27.x86_64
>    - nothing provides atomic-registries >= 1.19.1-6 needed by
> docker-2:1.13.1-42.git4402c09.fc27.x86_64
>   Problem 2: package kubernetes-node-1.7.3-1.fc27.x86_64 requires docker, but none of the
> providers can be installed
>    - package docker-2:1.13.1-26.gitb5e3294.fc27.x86_64 requires docker-common =
> 2:1.13.1-26.gitb5e3294.fc27, but none of the providers can be installed
>    - cannot install both docker-common-2:1.13.1-42.git4402c09.fc27.x86_64 and
> docker-common-2:1.13.1-26.gitb5e3294.fc27.x86_64
>    - cannot install both docker-common-2:1.13.1-26.gitb5e3294.fc27.x86_64 and
> docker-common-2:1.13.1-42.git4402c09.fc27.x86_64
>    - cannot install the best update candidate for package
> kubernetes-node-1.7.3-1.fc27.x86_64
>    - cannot install the best update candidate for package
> docker-common-2:1.13.1-26.gitb5e3294.fc27.x86_64
>    - nothing provides atomic-registries >= 1.19.1-6 needed by
> docker-2:1.13.1-42.git4402c09.fc27.x86_64
>   Problem 3: problem with installed package docker-2:1.13.1-26.gitb5e3294.fc27.x86_64
>    - package docker-2:1.13.1-26.gitb5e3294.fc27.x86_64 requires docker-rhel-push-plugin =
> 2:1.13.1-26.gitb5e3294.fc27, but none of the providers can be installed
>    - cannot install both docker-rhel-push-plugin-2:1.13.1-42.git4402c09.fc27.x86_64 and
> docker-rhel-push-plugin-2:1.13.1-26.gitb5e3294.fc27.x86_64
>    - cannot install both docker-rhel-push-plugin-2:1.13.1-26.gitb5e3294.fc27.x86_64 and
> docker-rhel-push-plugin-2:1.13.1-42.git4402c09.fc27.x86_64
>    - cannot install the best update candidate for package
> docker-rhel-push-plugin-2:1.13.1-26.gitb5e3294.fc27.x86_64
>    - nothing provides atomic-registries >= 1.19.1-6 needed by
> docker-2:1.13.1-42.git4402c09.fc27.x86_64
>  ================================================================================
>   Package                  Arch    Version                        Repository
>                                                                             Size
>  ================================================================================
>  Skipping packages with conflicts:
>  (add '--best --allowerasing' to command line to force their upgrade):
>   docker-common            x86_64  2:1.13.1-42.git4402c09.fc27    updates   85 k
>   docker-rhel-push-plugin  x86_64  2:1.13.1-42.git4402c09.fc27    updates  1.7 M
>  Skipping packages with broken dependencies:
>   docker                   x86_64  2:1.13.1-42.git4402c09.fc27    updates   20 M
>
>  Transaction Summary
>  ================================================================================
>  Skip  3 Packages
>
>  Nothing to do.
>  Complete! 
What do you get when you add  '--best --allowerasing' to command line to force
their
upgrade?

On my system....

[egreshko@meimei ~]$ rpm -q docker docker-common docker-rhel-push-plugin
docker-1.13.1-42.git4402c09.fc27.x86_64
docker-common-1.13.1-42.git4402c09.fc27.x86_64
docker-rhel-push-plugin-1.13.1-42.git4402c09.fc27.x86_64

[egreshko@meimei ~]$ rpm -q kubernetes-node
kubernetes-node-1.7.3-1.fc27.x86_64


-- 
Fedora Users List - The place to go to speculate endlessly

[Robert P. J. Day]

On Sat, 25 Nov 2017, Ed Greshko wrote:

>  What do you get when you add  '--best --allowerasing' to
> command
>  line to force their upgrade? 
  that did it, thank you kindly.

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================

[John Mellor]

On Sat, 2017-11-25 at 06:29 -0500, Robert P. J. Day wrote:
>    just did a full upgrade to fedora 27 a few days ago, first couple
>  updates worked fine, then this .. thoughts? should i just wait for
>  upstream to fix itself?
>  
>  
>   Problem 1: cannot install the best update candidate for package
>  docker-2:1.13.1-26.gitb5e3294.fc27.x86_64
>    - nothing provides atomic-registries >= 1.19.1-6 needed by docker-
>  2:1.13.1-42.git4402c09.fc27.x86_64
>   Problem 2: package kubernetes-node-1.7.3-1.fc27.x86_64 requires
>  docker, but none of the providers can be installed
>    - package docker-2:1.13.1-26.gitb5e3294.fc27.x86_64 requires
>  docker-common = 2:1.13.1-26.gitb5e3294.fc27, but none of the
>  providers can be installed
>    - cannot install both docker-common-2:1.13.1-
>  42.git4402c09.fc27.x86_64 and docker-common-2:1.13.1-
>  26.gitb5e3294.fc27.x86_64
>    - cannot install both docker-common-2:1.13.1-
>  26.gitb5e3294.fc27.x86_64 and docker-common-2:1.13.1-
>  42.git4402c09.fc27.x86_64
>    - cannot install the best update candidate for package kubernetes-
>  node-1.7.3-1.fc27.x86_64
>    - cannot install the best update candidate for package docker-
>  common-2:1.13.1-26.gitb5e3294.fc27.x86_64
>    - nothing provides atomic-registries >= 1.19.1-6 needed by docker-
>  2:1.13.1-42.git4402c09.fc27.x86_64
>   Problem 3: problem with installed package docker-2:1.13.1-
>  26.gitb5e3294.fc27.x86_64
>    - package docker-2:1.13.1-26.gitb5e3294.fc27.x86_64 requires
>  docker-rhel-push-plugin = 2:1.13.1-26.gitb5e3294.fc27, but none of
>  the providers can be installed
>    - cannot install both docker-rhel-push-plugin-2:1.13.1-
>  42.git4402c09.fc27.x86_64 and docker-rhel-push-plugin-2:1.13.1-
>  26.gitb5e3294.fc27.x86_64
>    - cannot install both docker-rhel-push-plugin-2:1.13.1-
>  26.gitb5e3294.fc27.x86_64 and docker-rhel-push-plugin-2:1.13.1-
>  42.git4402c09.fc27.x86_64
>    - cannot install the best update candidate for package docker-rhel-
>  push-plugin-2:1.13.1-26.gitb5e3294.fc27.x86_64
>    - nothing provides atomic-registries >= 1.19.1-6 needed by docker-
>  2:1.13.1-42.git4402c09.fc27.x86_64
>  =====================================================================
>  ===========
>   Package                  Arch    Version                        Repo
>  sitory
>                                                                       
>        Size
>  =====================================================================
>  ===========
>  Skipping packages with conflicts:
>  (add '--best --allowerasing' to command line to force their upgrade):
>   docker-common            x86_64  2:1.13.1-
>  42.git4402c09.fc27    updates   85 k
>   docker-rhel-push-plugin  x86_64  2:1.13.1-
>  42.git4402c09.fc27    updates  1.7 M
>  Skipping packages with broken dependencies:
>   docker                   x86_64  2:1.13.1-
>  42.git4402c09.fc27    updates   20 M
>  
>  Transaction Summary
>  =====================================================================
>  ===========
>  Skip  3 Packages
>  
>  Nothing to do.
>  Complete! 
I have the same problem, presumaby attributable to a stuck mirror
problem.  I'll wait a few more days and maybe it will resolve itself...

On a higher level, why is Fedora still packaging the long-deprecated
docker branch instead of the more up-to-date and correct docker-ce
branch?  Can someone please fix this distro?