From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp1.migadu.com ([2001:41d0:303:e224::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms8.migadu.com with LMTPS id P+1hKm15/WXBewAA62LTzQ:P1 (envelope-from ) for ; Fri, 22 Mar 2024 13:28:29 +0100 Received: from aspmx1.migadu.com ([2001:41d0:303:e224::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp1.migadu.com with LMTPS id P+1hKm15/WXBewAA62LTzQ (envelope-from ) for ; Fri, 22 Mar 2024 13:28:29 +0100 X-Envelope-To: larch@yhetil.org Authentication-Results: aspmx1.migadu.com; dkim=none; dmarc=none; spf=pass (aspmx1.migadu.com: domain of "help-guix-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="help-guix-bounces+larch=yhetil.org@gnu.org" ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1711110509; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:list-id:list-help: list-unsubscribe:list-subscribe:list-post; bh=CF6LgAXb5nNJRi3KGbH043fPGciGBF94ZedBH/DYCOA=; b=fqN3IfGufa5P8aGPG2JHeLZPox5w9o0hAUA9zzSucAohbf/qm2WzDFf9g0FkE5rB082CaQ e5R5al0X2ibTB9YwKKXuRQF0e/96b9DL2OMo+r4iRiU8sYHzxWZGj8I1D6qPpv6jYXQljE qB+NcyYrjAjkxH3US+syUvjt/cZlTJfvHmOdJ5UFaqHrqgCcFI94ruvfhBHQOykGk5qJqg isQQfyjH93t1LySCMms9NHTABLSyi0rNDNCbNzz98w0r7GmZ5POZ9JOAcjNPZ5whzO8uYn c0BkAVoBXmcgJtA5H2x1eJ1RKHZozkhIUgZNGyzHJoGRFodobJd2CIUGoJluaA== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=none; dmarc=none; spf=pass (aspmx1.migadu.com: domain of "help-guix-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="help-guix-bounces+larch=yhetil.org@gnu.org" ARC-Seal: i=1; s=key1; d=yhetil.org; t=1711110509; a=rsa-sha256; cv=none; b=iVWiKQdVMr1LMGORcH6+k3XcM8tp82R/YpSg+T0eA8xniUbK3yoERsnoH5qsDzV5wMURbB NG5QwuAGEC/qHDhv67OHhnup7IkOhkssRQjRFzZdBtvAha6yEy32DKHRpZVgIBu66lxQmE 88zHdS6muWqowShecPoBaVPCLq2Y8oN8sLVPlkUZdS39wsFwME9Ziyt9OpM5+7y4FzlOIC KB6oIKtQ3oRfO8Sg1c3vLf/uBep0G0EpvXZm5Q/8fqedq4gZlHpBPVDEzWIG0rlmj1yVdx 0xiik8OSHXKMn7uOXpYbYb05XLj/FhRpc894z2quvg6Xs96RWS3mfB+q567B8A== Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 2EB681A29D for ; Fri, 22 Mar 2024 13:28:29 +0100 (CET) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rndzv-0004ND-SA; Fri, 22 Mar 2024 08:27:47 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rndzo-0004Mp-Oy for help-guix@gnu.org; Fri, 22 Mar 2024 08:27:42 -0400 Received: from mailout-l3b-97.contactoffice.com ([212.3.242.97]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rndzl-0007Yf-W8 for help-guix@gnu.org; Fri, 22 Mar 2024 08:27:40 -0400 Received: from fidget.co-bxl (fidget.co-bxl [10.2.0.33]) by mailout-l3b-97.contactoffice.com (Postfix) with ESMTP id A33C8EAB; Fri, 22 Mar 2024 13:27:33 +0100 (CET) Date: Fri, 22 Mar 2024 13:27:31 +0100 (CET) From: Samuel Schmidt To: Ian Eure Cc: help-guix@gnu.org, Rodrigo Morales Message-ID: <825543971.2540902.1711110451429@fidget.co-bxl> In-Reply-To: <871q88vbl5.fsf@meson> References: <87o7djlp9t.fsf@rodrigomorales.site> <87il3rr8as.fsf@rodrigomorales.site> <1490502251.1052552.1710098230842@fidget.co-bxl> <871q88vbl5.fsf@meson> Subject: Re: Error when trying to run "docker-compose up" MIME-Version: 1.0 X-Mailer: ContactOffice Mail X-ContactOffice-Account: com:183455178 Received-SPF: none client-ip=212.3.242.97; envelope-from=samuel@schmidt-contact.com; helo=mailout-l3b-97.contactoffice.com X-Spam_score_int: -25 X-Spam_score: -2.6 X-Spam_bar: -- X-Spam_report: (-2.6 / 5.0 requ) BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001 autolearn=ham autolearn_force=no X-Spam_action: no action Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: help-guix@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-guix-bounces+larch=yhetil.org@gnu.org Sender: help-guix-bounces+larch=yhetil.org@gnu.org X-Migadu-Country: US X-Migadu-Flow: FLOW_IN X-Migadu-Spam-Score: -6.42 X-Spam-Score: -6.42 X-Migadu-Queue-Id: 2EB681A29D X-Migadu-Scanner: mx12.migadu.com X-TUID: iCsOfCazlv/J Hello, here is a work around for running docker compose on guix, that worked for m= e: ''' mkdir .docker/cli-plugins curl -SL https://github.com/docker/compose/releases/download/v2.17.2/docker= -compose-linux-x86_64 -o $HOME/.docker/cli-plugins/docker-compose sudo chmod +x $HOME/.docker/cli-plugins/docker-compose """ Of course, anyone who wants to run this takes the risk to ensure everything= is correct/secure.=20 Best, Samuel Am 17.03.2024 um 21:16, Ian Eure schrieb: Samuel Schmidt writes: > Hello, > > I am facing the same problem, but I have to use docker-compose.=C2=A0 > I guess there are no plans to fix this atm? :/ Or did you find=20 > any help regarding this problem? > > Am 17.01.2024 um 21:53, Rodrigo Morales =20 > schrieb:Rodrigo Morales writes: > >> Does anyone know what could be the problem? > > I found this thread [1] on help-guix from 2019 where a user=20 > reports > having errores with docker-compose. A user replies: > > #+BEGIN_QUOTE > The root of this problem is that our docker-compose package is=20 > very > old: it was added in January 2016(!), and has never been updated > since. I guess that proves how unneccessary Docker is once=20 > you've > discovered Guix=E2=80=A6 ducks > #+END_QUOTE > > Furthermore, I noticed that the version of docker-compose is=20 > 1.29.2 and > upstream [2] is at 2.12.0, so even if I fix this problem. I'll=20 > be using > an old version of docker-compose. For my use case, it would be=20 > more > useful to use the latest version of docker-compose, so if I=20 > wanted to > use docker-compose under Guix, I would need for me to write a=20 > Guix > package for that version. > Note also that this is a Docker Compose v1->v2 upgrade. The newer=20 version is completely different from v1, it=E2=80=99s a plugin that=20 integrates with the Docker CLI, so you run `docker compose' rather=20 than `docker-compose'. We likely need a completely new package=20 for it. > I have one question: The user above states that Docker is=20 > unnecessary > once you have discovered Guix. I have been using Guix for around=20 > 6 > months, but I don't see how I could use Guix for running a web=20 > server on > a container that uses node.js and postgresql. The reason why I=20 > initially > wanted to use docker is because I find it more convenient to run=20 > a web > server with node.js and postgresql. Any information on this=20 > topic is > appreciated. > I continue to find both Guix and Docker useful. While they have=20 some overlapping goals, I don=E2=80=99t believe either can replace the=20 other. The closest thing to Docker Compose I=E2=80=99m aware of that you can do=20 with pure Guix is create an operating-system with the services you=20 want to run, then use `guix system image -t docker=20 my-machine-definition.scm' to bundle it as a Docker image. This=20 will bring up a container with the base Guix and those services=20 running inside. This setup lacks some niceties which Compose has: Everything seems to run in the same namespace[1], so a compromise=20 of one service is more likely to compromise the whole system.=20 Compose is more resistant to this, since each service runs in its=20 own namespace (that is, container). I don=E2=80=99t know of a Guix=20 equivalent for the Compose style of multi-container setup. I haven=E2=80=99t compared, but I strongly suspect the image sizes are=20 larger than an equivalent plain Docker image, due to having the=20 base Guix inside them, whereas many Docker images use (or have the=20 option of) an Alpine base. It can only run things with a Guix package and Shepherd service to=20 manage it. Updates are likely slower than vendor-provided Docker images. It=E2=80=99s also a more involved setup -- you have to write the config,=20 and build the image, and load it, and run it. In fact, I have yet=20 to actually make a system image that works *at all*. Compose is=20 dead simple in comparison. =E2=80=94 Ian [1]: At least, if Shepherd can run services in their own=20 namespaces, like Docker can, the manual is silent on the topic.