Hello, I am facing the same problem, but I have to use docker-compose. I guess there are no plans to fix this atm? :/ Or did you find any help regarding this problem?
Am 17.01.2024 um 21:53, Rodrigo Morales <m...@rodrigomorales.site> schrieb:Rodrigo Morales <m...@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
