On Mon, 2017-03-20 at 00:27:27 +0700, Willy Sudiarto Raharjo wrote: > > It's been a week and Asaf hasn't replied neither directly to me nor to > > this list. Meanwhile I updated the scripts for version 17.03.0 and have > > been using them without any problems at work. > > > > Question to the admins: should I wait longer or should I take over > > ownership and submit updated SlackBuilds for runc, containerd and > > docker? > > push it
Went ahead and pushed the updates (and a couple of new submissions as well). Docker set of packages now consists of: runc containerd docker-proxy tini docker All components use exact git commits expected by docker 17.3.0. As for additional tool docker-compose, you can fetch it from https://github.com/docker/compose/releases by following provided instructions or (since it's a Python app) install it inside virtualenv (works with both Python 2 and 3) using: pip install docker-compose It seems that there will be a new version (17.3.1) released next Monday (currently at rc1), but I thought that it's better to push scripts for version I've been testing the last few days and know that it's functioning correctly. -- Audrius Kažukauskas
signature.asc
Description: PGP signature
_______________________________________________ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
