Bug 1457376

Summary: After upgrade to docker-compose-1.9.0-3.fc25.noarch, docker-compose up fails to run due to missing dependencies
Product: [Fedora] Fedora Reporter: Jan Pazdziora (Red Hat) <jpazdziora>
Component: docker-composeAssignee: Michael Hampton <error>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 25CC: error, jpazdziora, roman, ttomecek
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: docker-compose-1.9.0-4.fc25 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-06-09 11:30:11 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 Jan Pazdziora (Red Hat) 2017-05-31 15:27:35 UTC
Description of problem:

I've had working docker-compose-1.8.1-1.fc25.noarch setup. I've upgraded the package to the latest greatest and docker-compose up stop to work.

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

docker-compose-1.9.0-3.fc25.noarch

How reproducible:

Deterministic.

Steps to Reproduce:
1. Have a working setup with Fedora 25 GA docker-compose version (1.8.1-1.fc25).
2. Check that docker-compose up works. Even running it in directory with no docker-compose.yml should give decent output:

ERROR: 
        Can't find a suitable configuration file in this directory or any
        parent. Are you in the right directory?

        Supported filenames: docker-compose.yml, docker-compose.yaml

3. Upgrade docker-compose.
4. Run docker-compose up.

Actual results:

# docker-compose up
Traceback (most recent call last):
  File "/usr/bin/docker-compose", line 5, in <module>
    from pkg_resources import load_entry_point
  File "/usr/lib/python2.7/site-packages/pkg_resources/__init__.py", line 2958, in <module>
    @_call_aside
  File "/usr/lib/python2.7/site-packages/pkg_resources/__init__.py", line 2944, in _call_aside
    f(*args, **kwargs)
  File "/usr/lib/python2.7/site-packages/pkg_resources/__init__.py", line 2971, in _initialize_master_working_set
    working_set = WorkingSet._build_master()
  File "/usr/lib/python2.7/site-packages/pkg_resources/__init__.py", line 637, in _build_master
    return cls._build_from_requirements(__requires__)
  File "/usr/lib/python2.7/site-packages/pkg_resources/__init__.py", line 650, in _build_from_requirements
    dists = ws.resolve(reqs, Environment())
  File "/usr/lib/python2.7/site-packages/pkg_resources/__init__.py", line 829, in resolve
    raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: The 'docker-py>=1.10.6' distribution was not found and is required by docker-compose

Expected results:

ERROR: 
        Can't find a suitable configuration file in this directory or any
        parent. Are you in the right directory?

        Supported filenames: docker-compose.yml, docker-compose.yaml

or containers properly started.

Additional info:

Comment 1 Jan Pazdziora (Red Hat) 2017-05-31 15:30:02 UTC
Running

dnf upgrade python-docker-py

to get python-docker-py-1.10.6-1.fc25.noarch seems to workaround the issue.

Comment 2 Fedora Update System 2017-05-31 16:17:44 UTC
docker-compose-1.9.0-4.fc25 has been submitted as an update to Fedora 25. https://bodhi.fedoraproject.org/updates/FEDORA-2017-174752b4a4

Comment 3 Fedora Update System 2017-06-01 07:08:33 UTC
docker-compose-1.9.0-4.fc25 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-174752b4a4

Comment 4 Fedora Update System 2017-06-09 11:30:11 UTC
docker-compose-1.9.0-4.fc25 has been pushed to the Fedora 25 stable repository. If problems still persist, please make note of it in this bug report.