Laravel-echo-server Error

[NetBT]

Info:

• Docker version ($ docker --version): 19.03.2
• Laradock commit ($ git rev-parse HEAD): 99da6ff60ceb5027d45cc3f3a023c481cae8b923
• System info (Mac, PC, Linux): PC
• System info disto/version: Win 10

Issue:

When I started laravel-echo-server.An error occurred as below:
laravel-echo-server_1 | npm WARN using --force I sure hope you know what you are doing.
laravel-echo-server_1 |
laravel-echo-server_1 | > laravel-echo-server-docker@0.0.1 start /usr/src/app
laravel-echo-server_1 | > laravel-echo-server start
laravel-echo-server_1 |
laravel-echo-server_1 | Error: There is already a server running! Use the option '--force' to stop it and start another one.
laradock_laravel-echo-server_1 exited with code 0

---

Expected behavior:

---

Reproduce:

I dont know, sometimes it will be OK.

---

Relevant Code:

// place a code sample here

[perezale]

Same here!!

If I run docker-compose run laravel-echo-server npm start everything goes alright

[josesdev]

I rebuilt this service and then start it again and worked:

$ docker-compose build --no-cache laravel-echo-server
$ docker-compose up laravel-echo-server

[stale]

Hi 👋 this issue has been automatically marked as stale 📌 because it has not had recent activity 😴. It will be closed if no further activity occurs. Thank you for your contributions ❤️.

[stale]

Hi again 👋 we would like to inform you that this issue has been automatically closed 🔒 because it had not recent activity during the stale period. We really really appreciate your contributions, and looking forward for more in the future 🎈.

[cgrinker]

I ran into this problem today. I believe it stems from the laravel-echo-server.lock file being stored on your host volume. Removing the lockfile fixed the problem from me.

[ash-rain]

...it stems from the laravel-echo-server.lock file being stored on your host volume. Removing the lockfile fixed the problem from me.

Thank you this saved me!

[mavazca]

How do I remove laravel-echo-server.lock file?