Provide RPM and DEB packages for compose

[dnephin]

Not everyone likes to install binaries (#1288).

It might be good to provide a system package for compose. We should use https://github.com/spotify/dh-virtualenv for the debian package and look into a similar approach for the rpm.

[jacek99]

I would recommend to just work with the respective Debian and Fedora/CentOS communities and get that rolled into the default system repositories.'

Just my $0.02

[atrauzzi]

That ends up being less than optimal for a project that's moving as quickly as compose. You'll just end up with a pile of people coming in reporting that new features aren't working.

Better to have a PPA so that you can do updates outside of the distro release cycle.

[dnephin]

It sounds like there is a deb for it (https://packages.debian.org/sid/docker-compose) but it's already a few versions behind.

[dnephin]

And a fedora package https://admin.fedoraproject.org/pkgdb/package/docker-compose/

Couldn't this be done in the same way as https://docs.docker.com/installation/ubuntulinux/ and https://docs.docker.com/installation/fedora/? i.e. host on *.docker.org

[dnephin]

Hosting the packages is the easy part. Most of the work here is making sure the package works for older versions of distros.

[athyuttamre]

Would you consider doing this once development pace has stabilized?

[StefanScherer]

What about putting the docker-compose binary that is also available at the GH release into DEB/RPM?
No python/virtualenv required on the target machine.

Creating such a package with fpm should be very easy. We've done similar things at work (sorry private repos) and put some integration tests behind the build to test the DEB/RPM package at CircleCI within debian/centos Docker containers.

If there is interest in such things I can check if we can open source that parts as an example.

[alexanderadam]

I totally agree that it would nice to have it packaged but for ubuntu I don't think it's useful to add another PPA. I would rather like to see current docker compose in the already existing repository.

@dnephin apt repositories can have different packages per distribution anyway and as the other docker packages are already included it even should be easier to manage that compose and docker work nicely together.

Therefore I think providing automatic builds for the official docker repos should be in focus here (and not creating additional repositories).