# Why is the docker-compose package gone?

**URL:** <https://forums.suse.com/t/why-is-the-docker-compose-package-gone/28532>\
**Category:** SLES Virtualization\
**Created:** [August 16, 2016, 11:37am UTC](https://forums.suse.com/t/why-is-the-docker-compose-package-gone/28532 "2016-08-16T11:37:31Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![enovaklbank](https://avatars.discourse-cdn.com/v4/letter/e/aca169/32.png) [@enovaklbank](https://forums.suse.com/u/enovaklbank)\
**Post date:** [August 16, 2016, 11:37am UTC](https://forums.suse.com/t/why-is-the-docker-compose-package-gone/28532/1 "2016-08-16T11:37:31Z")

</div>

Hi all,

I’ve installed a server some weeks ago with SLES12-SP1, and had docker-compose (1.2.0-2.1) in the Container module. The only glitch was that I needed to downgrade the python-requests package as suggested in this kbarticle: [https://www.novell.com/support/kb/doc.php?id=7017258](https://www.novell.com/support/kb/doc.php?id=7017258)  
Note: “Interim solution until this will be resolved in code” - from February 2016.

Now I wanted to install another server, but can’t find the package anymore. Why is it gone? Does someone has any information regarding this change?

[QUOTE]lxelkp1k:~ # env LANG=en\_US.UTF-8 zypper se docker-compose  
Loading repository data…  
Reading installed packages…  
No packages found.[/QUOTE]

Thanks.

---

<div class="post-metadata">

**Author:** ![enovaklbank](https://avatars.discourse-cdn.com/v4/letter/e/aca169/32.png) [@enovaklbank](https://forums.suse.com/u/enovaklbank)\
**Post date:** [August 16, 2016, 12:00pm UTC](https://forums.suse.com/t/why-is-the-docker-compose-package-gone/28532/2 "2016-08-16T12:00:28Z")

</div>

The workaround is of course very simple, but that does explain why the package can’t be installed by zypper.

`zypper in python-PyYAML python-setuptools python-texttable python-websocket-client python-dockerpty python-docker-py python-docopt
wget http://<your-update-server>/repo/SUSE/Updates/SLE-Module-Containers/12/x86_64/update/noarch/docker-compose-1.2.0-2.1.noarch.rpm
rpm -Uvh docker-compose-1.2.0-2.1.noarch.rpm`

The package is in the repository but can not be found/installed using zypper.

---

<div class="post-metadata">

**Author:** ![swadm](https://avatars.discourse-cdn.com/v4/letter/s/bc79bd/32.png) [@swadm](https://forums.suse.com/u/swadm)\
**Post date:** [February 23, 2017, 12:23pm UTC](https://forums.suse.com/t/why-is-the-docker-compose-package-gone/28532/3 "2017-02-23T12:23:17Z")

</div>

Support told me that docker-compose packet was only provided as tech preview in SLES12 and has been dropped because of “invasive dependencies”. They pointed me to Kubernetes as supported solution.

Comments on that decision? I have the impression that Kubernetes as a replacement for docker-compose is like to taking a sledgehammer to crack a nut?

Tom

---

<div class="post-metadata">

**Author:** ![RogerIThomas](https://avatars.discourse-cdn.com/v4/letter/r/7993a0/32.png) [@RogerIThomas](https://forums.suse.com/u/RogerIThomas)\
**Post date:** [March 13, 2018, 10:21pm UTC](https://forums.suse.com/t/why-is-the-docker-compose-package-gone/28532/4 "2018-03-13T22:21:39Z")

</div>

[QUOTE=swadm;36707]Support told me that docker-compose packet was only provided as tech preview in SLES12 and has been dropped because of “invasive dependencies”. They pointed me to Kubernetes as supported solution.

Comments on that decision? I have the impression that Kubernetes as a replacement for docker-compose is like to taking a sledgehammer to crack a nut?

Tom[/QUOTE]

I think the support team need to remember that users are trying to use the OS as a platform to do things, rather than re-invent solutions that already work/deploy on other platforms. If they have found issues with docker-compose it would be great for them to document them, but docker-compose is still a required solution to get many things done.

---

<div class="post-metadata">

**Author:** ![RogerIThomas](https://avatars.discourse-cdn.com/v4/letter/r/7993a0/32.png) [@RogerIThomas](https://forums.suse.com/u/RogerIThomas)\
**Post date:** [March 15, 2018, 3:44pm UTC](https://forums.suse.com/t/why-is-the-docker-compose-package-gone/28532/5 "2018-03-15T15:44:08Z")

</div>

Quick update, after some hunting the best solution I have found is to use the third party OBS release found here

```
   [url]https://build.opensuse.org/package/show/home:M0ses:Infrastructure/docker-compose[/url]

```

It does get a bit messy as other packages are then needed from OBS and currently I have got as far as including both

```
  python-dockerpty from [url]https://build.opensuse.org/project/show/Virtualization:containers[/url]
  python-PySocks from [url]https://build.opensuse.org/package/show/Cloud%3AOpenStack%3AMaster/python-PySocks[/url]

```

This gets me as far as docker-compose passing it’s own internal checks at the command line. As I learn/understand more I will try and post an update.

---

<div class="post-metadata">

**Author:** ![Jens-U](https://avatars.discourse-cdn.com/v4/letter/j/d78d45/32.png) [@Jens-U](https://forums.suse.com/u/Jens-U)\
**Post date:** [March 19, 2018, 3:49pm UTC](https://forums.suse.com/t/why-is-the-docker-compose-package-gone/28532/6 "2018-03-19T15:49:48Z")

</div>

> [@RogerIThomas;51506](#):
>
> I think the support team need to remember that users are trying to use the OS as a platform to do things, rather than re-invent solutions that already work/deploy on other platforms. If they have found issues with docker-compose it would be great for them to document them[…]

[QUOTE=RogerIThomas;51563]Quick update, […]  
It does get a bit messy as other packages are then needed from OBS[/QUOTE]

So maybe have a look at support’s statement again, as relayed by Tom:

> Support told me that docker-compose packet […] has been dropped because of “invasive dependencies”.

😉

Regards,  
J

---

<div class="post-metadata">

**Author:** ![sdhaval](https://avatars.discourse-cdn.com/v4/letter/s/96bed5/32.png) [@sdhaval](https://forums.suse.com/u/sdhaval)\
**Post date:** [April 2, 2018, 1:06pm UTC](https://forums.suse.com/t/why-is-the-docker-compose-package-gone/28532/7 "2018-04-02T13:06:36Z")

</div>

Hello,

I ran into this requirement as well and tried installing number of rpms. Finally I had to give up as I ended up with conflicts all around. It is then that i stumbled on the web that it would be easier to use “pip”. And use this python package management tool to install docker-compose.

```auto
zypper install python-pip
```

```auto
pip install -U docker-compose
```

-Thanks,  
Dhaval

---

<div class="post-metadata">

**Author:** ![malcolmlewis](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/malcolmlewis/32/11375_2.png) [@malcolmlewis](https://forums.suse.com/u/malcolmlewis)\
**Post date:** [April 2, 2018, 5:06pm UTC](https://forums.suse.com/t/why-is-the-docker-compose-package-gone/28532/8 "2018-04-02T17:06:52Z")

</div>

Hi  
But if you add SUSE Package Hub repository, it’s available there;  
[https://packagehub.suse.com/packages/docker-compose/](https://packagehub.suse.com/packages/docker-compose/)

By using Package Hub the system will still be supported, not the package… See [https://packagehub.suse.com/#features](https://packagehub.suse.com/#features)
