Bug 1012302

Summary: Snapshot 20161125 docker & containerd have unresolvable runc depedency
Product: [openSUSE] openSUSE Tumbleweed Reporter: Pieter Hollants <pfhllnts>
Component: OtherAssignee: Flavio Castelli <fcastelli>
Status: RESOLVED FIXED QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P5 - None CC: asarai, forgotten_MM7mTieSEI, forgotten_qsLRgSAYJY, jordimassaguerpla, miso, okurz
Version: CurrentFlags: asarai: needinfo? (jordimassaguerpla)
Target Milestone: ---   
Hardware: x86-64   
OS: Other   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Pieter Hollants 2016-11-27 22:41:46 UTC
The new 20161125 snapshot has an unresolvable runc dependency for docker/containerd:

e7450:/home/pief # grep VERSION /etc/os-release 
# VERSION="20161125"
VERSION_ID="20161125"
e7450:/home/pief # zypper lr
Repository priorities in effect:                                                                                                                              (See 'zypper lr -P' for details)
      98 (raised priority)  :  1 repository  
      99 (default priority) :  6 repositories
     100 (lowered priority) :  1 repository  
     120 (lowered priority) :  1 repository  

#  | Alias            | Name                                     | Enabled | GPG Check | Refresh
---+------------------+------------------------------------------+---------+-----------+--------
 1 | Essentials       | Packman Essentials                       | Yes     | (r ) Yes  | Yes    
 2 | Tumbleweed       | videolan.org                             | Yes     | (r ) Yes  | Yes    
 3 | google-chrome    | google-chrome                            | No      | ----      | ----   
 4 | repo-debug       | repo-debug                               | Yes     | (r ) Yes  | Yes    
 5 | repo-non-oss     | repo-non-oss                             | Yes     | (r ) Yes  | Yes    
 6 | repo-oss         | repo-oss                                 | Yes     | (r ) Yes  | Yes    
 7 | repo-src-non-oss | repo-src-non-oss                         | Yes     | (r ) Yes  | Yes    
 8 | repo-src-oss     | repo-src-oss                             | Yes     | (r ) Yes  | Yes    
 9 | repo-update      | repo-update                              | Yes     | (r ) Yes  | Yes    
10 | virtualbox       | VirtualBox for openSUSE 13.2 / Leap 42.1 | Yes     | ( p) Yes  | Yes    
e7450:/home/pief # zypper install docker
Loading repository data...
Reading installed packages...
Resolving package dependencies...

Problem: nothing provides runc = 0.1.1+git02f8fa7 needed by docker-1.12.3-1.2.x86_64
 Solution 1: do not install docker-1.12.3-1.2.x86_64
 Solution 2: break docker-1.12.3-1.2.x86_64 by ignoring some of its dependencies

Choose from above solutions by number or cancel [1/2/c] (c): 

Same for containerd.

(BTW, there is no "Container" component in Bugzilla, maybe we'd like to add it?)
Comment 1 Aleksa Sarai 2016-11-28 04:38:55 UTC
It looks like this is probably related to the very-recently-fixed bsc#1009961.
Comment 2 Forgotten User MM7mTieSEI 2016-11-28 14:05:05 UTC
Doing a dist-upgrade with docker installed I get

2 Problems:
Problem: docker-1.12.3-1.2.x86_64 requires containerd = 0.2.4+git0366d7e, but this requirement cannot be provided
Problem: docker-1.12.3-1.1.x86_64 requires runc = 0.1.1+git02f8fa7, but this requirement cannot be provided

Problem: docker-1.12.3-1.2.x86_64 requires containerd = 0.2.4+git0366d7e, but this requirement cannot be provided
  deleted providers: containerd-0.2.4+git0366d7e-1.1.x86_64
 Solution 1: Following actions will be done:
  deinstallation of docker-1.12.3-1.1.x86_64
  deinstallation of docker-bash-completion-1.12.3-1.1.noarch
 Solution 2: keep obsolete containerd-0.2.4+git0366d7e-1.1.x86_64
 Solution 3: break docker-1.12.3-1.2.x86_64 by ignoring some of its dependencies

Choose from above solutions by number or skip, retry or cancel [1/2/3/s/r/c] (c): 2

Problem: docker-1.12.3-1.1.x86_64 requires runc = 0.1.1+git02f8fa7, but this requirement cannot be provided
  deleted providers: runc-0.1.1+git02f8fa7-1.1.x86_64
 Solution 1: Following actions will be done:
  deinstallation of docker-zsh-completion-1.12.3-1.1.noarch
  deinstallation of docker-bash-completion-1.12.3-1.1.noarch
 Solution 2: keep obsolete runc-0.1.1+git02f8fa7-1.1.x86_64
 Solution 3: break docker-1.12.3-1.1.x86_64 by ignoring some of its dependencies

Choose from above solutions by number or skip, retry or cancel [1/2/3/s/r/c] (c): 2


(In reply to Aleksa Sarai from comment #1)
> It looks like this is probably related to the very-recently-fixed
> bsc#1009961.

I'm not that sure, the message from 2016-11-25 refers to leap 42.1 and 42.2.
Comment 3 Aleksa Sarai 2016-11-28 14:07:10 UTC
> (In reply to Aleksa Sarai from comment #1)
> > It looks like this is probably related to the very-recently-fixed
> > bsc#1009961.
> 
> I'm not that sure, the message from 2016-11-25 refers to leap 42.1 and 42.2.

Yes, but the packages both come from Virtualization:containers (and the versioning issue came from there). I'll check if there's an open submission for Factory.
Comment 4 Forgotten User MM7mTieSEI 2016-11-28 14:15:54 UTC
(In reply to Aleksa Sarai from comment #3)
> Yes, but the packages both come from Virtualization:containers (and the
> versioning issue came from there).

I see.

> I'll check if there's an open submission
> for Factory.

Thank you!
Comment 5 Aleksa Sarai 2016-11-28 14:41:14 UTC
> > I'll check if there's an open submission
> > for Factory.
> 
> Thank you!

The change has been merged into openSUSE:Factory four days ago. So I'm fairly sure that this should be released in the next snapshot. As far as I can tell, you don't have the latest from openSUSE:Factory (the version "runc-0.1.1+git02f8fa7-1.1.x86_64" is wrong if the patch had been applied).
Comment 6 Forgotten User MM7mTieSEI 2016-11-28 14:52:02 UTC
(In reply to Aleksa Sarai from comment #5)
> 
> The change has been merged into openSUSE:Factory four days ago. So I'm
> fairly sure that this should be released in the next snapshot. 

great.

> As far as I
> can tell, you don't have the latest from openSUSE:Factory (the version
> "runc-0.1.1+git02f8fa7-1.1.x86_64" is wrong if the patch had been applied).

right now I'm on 20161123.

-> zypper info runc
Loading repository data...
Reading installed packages...


Information for package runc:
-----------------------------
Repository     : repo-oss
Name           : runc
Version        : 0.1.1+gitr2816_02f8fa7-1.1
Arch           : x86_64
Vendor         : openSUSE
Installed Size : 4.8 MiB
Installed      : Yes
Status         : out-of-date (version 0.1.1+git02f8fa7-1.1 installed)
Summary        : Tool for spawning and running OCI containers
Comment 7 Aleksa Sarai 2016-11-28 15:24:09 UTC
@Jordi: Why hasn't the Docker package been updated? It looks like we're pinning the old version still (which is why they can't update on TW):

# Containerd and runC are required as they are the only currently supported
# execdrivers of Docker. NOTE: The version pinning here matches upstream's
# Dockerfile to ensure that we don't use a slightly incompatible version of
# runC or containerd (which would be bad).
Requires:       containerd = 0.2.4+git0366d7e
Requires:       runc = 0.1.1+git02f8fa7
Comment 8 Aleksa Sarai 2016-11-28 15:29:48 UTC
Ah, okay. There's an open sr#1012302 (which fixes Docker). But it's blocked because it looks like we haven't pushed a fixed version of containerd (the current version of containerd in Factory doesn't pin the right runC version).

I've opened sr#442436 to fix containerd.
Comment 9 Bernhard Wiedemann 2016-11-28 17:00:24 UTC
This is an autogenerated message for OBS integration:
This bug (1012302) was mentioned in
https://build.opensuse.org/request/show/442436 Factory / containerd
Comment 10 Dominique Leuenberger 2016-11-29 09:27:10 UTC
*** Bug 1012540 has been marked as a duplicate of this bug. ***
Comment 11 Forgotten User MM7mTieSEI 2016-12-01 21:30:29 UTC
I just updated to TW20161129 and the problem went away.

Thank you very much for solving the problem.

ps: I don't dare marking the bug as resolved
Comment 12 Pieter Hollants 2016-12-02 10:36:11 UTC
But I do :) Confirming fixed on Tumbleweed 20161128, thanks for fixing!