From: Tobias Geerinckx-Rice <me@tobias.gr>
To: help-guix@gnu.org
Subject: Re: docker-compose not work
Date: Sun, 16 Jun 2019 19:46:02 +0200 [thread overview]
Message-ID: <87blyxwhid.fsf@nckx> (raw)
In-Reply-To: <6d37df3c18bfe7282530b84440454118@disroot.org>
[-- Attachment #1: Type: text/plain, Size: 1354 bytes --]
Arkhan,
arkhan@disroot.org wrote:
> regards,
Hullo, and welcome to Guix!
> install docker and docker-compose but at the time of executing
> it I have the following error
[…]
> pkg_resources.DistributionNotFound: The 'jsonschema<3,>=2.5.1'
> distribution was not found and is required by docker-compose
>
> apparently the dependencies of this package are wrong,
>
> someone can tell me how I can solve it.
The root of this problem is that our docker-compose package is
*very* old: it was added in January 2016(!), and has never been
updated since. I guess that proves how unneccessary Docker is
once you've discovered Guix… *ducks*
We have docker-compose 1.5.2. Upstream is currently at 1.24.0.
Updating it probably won't be trivial (although I haven't checked
in detail—it might be).
However, even 1.24.0 complains about jsonschema<3,>=2.5.1 not
being found. Since Docker insists on using an old library, and I
don't feel comfortable removing the version constraints (I don't
use Docker), I've added it back on master and told docker-compose
to use it.
Could you guix pull and try an updated docker-compose? If you're
very lucky, this more than 3-year-old piece of software will just
work. If not, please open a bug by sending your message to
bug-guix@gnu.org.
Thanks!
T G-R
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2019-06-16 17:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-16 15:28 docker-compose not work arkhan
2019-06-16 17:46 ` Tobias Geerinckx-Rice [this message]
2019-06-17 0:42 ` Edison Ibáñez
2019-06-17 1:27 ` Tobias Geerinckx-Rice
2019-06-18 9:10 ` Björn Höfling
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87blyxwhid.fsf@nckx \
--to=me@tobias.gr \
--cc=help-guix@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).