Unable to run link-warden through docker-compose about linkwarden

[moeenaslam]

You have to run it with docker compose instead of docker-compose. To run, use docker compose up.
This project uses docker compose V2 and I can say that if you execute docker-compose -v, it will show you version 1.xx.xx whereas now docker comes with compose v2.

[axsddlr]

+1 to this

[burkely-00orso69]

same unfotunately...

[nevertomorrow]

@moeenaslam Thanks for the suggestion. However, I don't think it is working on my end even if I switched to docker compose.
Here's what I've done.

$ mkdir -p ~/.docker/cli-plugins/
$ curl -SL https://github.com/docker/compose/releases/download/v2.6.1/docker-compose-linux-x86_64 -o ~/.docker/cli-plugins/docker-compose
$ chmod +x ~/.docker/cli-plugins/docker-compose

Then I made a quick test

$ docker-compose version
docker-compose version 1.25.0, build unknown
docker-py version: 4.1.0
CPython version: 3.8.10
OpenSSL version: OpenSSL 1.1.1f  31 Mar 2020

$ docker compose version
Docker Compose version v2.6.1

Started with docker compose

$ cd link-warden/
$ docker compose up -d
[+] Running 4/4
 ⠿ Network link-warden_default              Created                                                                0.1s
 ⠿ Container link-warden-mongo-1            Started                                                                0.4s
 ⠿ Container link-warden-link-warden-api-1  Started                                                                0.7s
 ⠿ Container link-warden-link-warden-1      Started                                                                1.0s

However, it was still with same issue

$ docker ps
CONTAINER ID   IMAGE                          COMMAND                  CREATED         STATUS                          PORTS                                                                                                                                                                       NAMES
62068e10300c   link-warden_link-warden        "docker-entrypoint.s…"   8 seconds ago   Restarting (127) 1 second ago                                                                                                                                                                               link-warden-link-warden-1
db5808576db5   link-warden_link-warden-api    "docker-entrypoint.s…"   8 seconds ago   Restarting (1) 1 second ago                                                                                                                                                                                 link-warden-link-warden-api-1

The error logs are the same as I pasted previously.

[nevertomorrow]

Ok, I made a fresh start by deleting all the existing images + git folder

I used docker compose up -d this time and it's working as expected.

One more thing I should mention is I also tried to use Dockerfile.prod as Dockerfile and it's not working for link-warden_link-warden
link-warden_link-warden is still restarting with error in log:

/docker-entrypoint.sh: exec: line 38: npm: not found

I did noticed a few warnings during build, unfortunately, I didn't capture all of them as they rolled over quickly.

=> => # found 0 vulnerabilities
 => => # npm WARN EBADENGINE Unsupported engine {
 => => # npm WARN EBADENGINE   package: '[email protected]',
 => => # npm WARN EBADENGINE   required: { npm: 'please-use-yarn', yarn: '>= 1.19.1' },
 => => # npm WARN EBADENGINE   current: { node: 'v18.4.0', npm: '8.14.0' }
 => => # npm WARN EBADENGINE }

 => => # npm WARN deprecated [email protected]: See https://github.com/lydell/source-map-resolve#deprecated
 => => # npm WARN deprecated [email protected]: This SVGO version is no longer supported. Upgrade to v2.x.x.

  => => # To address all issues (including breaking changes), run:
 => => #   npm audit fix --force
 => => # Run `npm audit` for details.
 => => # > [email protected] build
 => => # > react-scripts build

Using the default Dockerfile (dev version as mentioned in the file) is ok to make the whole app running.

@daniel31x13 Could you update your README.md to emphasize that this project should be using docker compose V2 so that the other users could avoid this issue.

Thanks all.

[daniel31x13]

Hello @nevertomorrow,
Sorry to be unresponsive.
I applied the changes.

[melyux]

Got this error and never got the project running. Using docker compose v2. Tried deleting the images and the git folder and trying again, with no luck.