From: Rodrigo Morales <me@rodrigomorales.site>
To: <help-guix@gnu.org>
Subject: Re: Error when trying to run "docker-compose up"
Date: Wed, 17 Jan 2024 15:53:15 -0500 [thread overview]
Message-ID: <87il3rr8as.fsf@rodrigomorales.site> (raw)
In-Reply-To: <87o7djlp9t.fsf@rodrigomorales.site>
Rodrigo Morales <me@rodrigomorales.site> writes:
> Does anyone know what could be the problem?
I found this thread [1] on help-guix from 2019 where a user reports
having errores with docker-compose. A user replies:
#+BEGIN_QUOTE
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*
#+END_QUOTE
Furthermore, I noticed that the version of docker-compose is 1.29.2 and
upstream [2] is at 2.12.0, so even if I fix this problem. I'll be using
an old version of docker-compose. For my use case, it would be more
useful to use the latest version of docker-compose, so if I wanted to
use docker-compose under Guix, I would need for me to write a Guix
package for that version.
I have one question: The user above states that Docker is unnecessary
once you have discovered Guix. I have been using Guix for around 6
months, but I don't see how I could use Guix for running a web server on
a container that uses node.js and postgresql. The reason why I initially
wanted to use docker is because I find it more convenient to run a web
server with node.js and postgresql. Any information on this topic is
appreciated.
[1] https://lists.gnu.org/archive/html/help-guix/2019-06/msg00182.html
[2] https://github.com/docker/compose/releases
next prev parent reply other threads:[~2024-01-17 20:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-17 19:43 Error when trying to run "docker-compose up" Rodrigo Morales
2024-01-17 20:53 ` Rodrigo Morales [this message]
2024-01-17 21:05 ` Rodrigo Morales
2024-01-17 21:30 ` Rodrigo Morales
2024-03-10 19:17 ` Samuel Schmidt
2024-03-10 19:25 ` Tomas Volf
2024-03-17 20:16 ` Ian Eure
2024-03-22 12:27 ` Samuel Schmidt
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=87il3rr8as.fsf@rodrigomorales.site \
--to=me@rodrigomorales.site \
--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).