Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to install Panache with docker on a debian OS. #37

Open
flegeai opened this issue Oct 11, 2023 · 3 comments
Open

Unable to install Panache with docker on a debian OS. #37

flegeai opened this issue Oct 11, 2023 · 3 comments

Comments

@flegeai
Copy link

flegeai commented Oct 11, 2023

Hi,
I'd like to run Panache on my own laptop as well as a debian VM on a cloud. But when running the docker-compose up, I get the following error message :

Starting panache ... done
Attaching to panache
panache | Starting nginx: nginx.
panache | npm WARN read-shrinkwrap This version of npm is compatible with lockfileVersion@1, but package-lock.json was generated for lockfileVersion@2. I'll try to do my best with it!
panache | npm WARN deprecated [email protected]: The v1 package contains DANGEROUS / INSECURE binaries. Upgrade to safe fsevents v2
panache | npm ERR! code EBADPLATFORM
panache | npm ERR! notsup Unsupported platform for [email protected]: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
panache | npm ERR! notsup Valid OS:    darwin
panache | npm ERR! notsup Valid Arch:  any
panache | npm ERR! notsup Actual OS:   linux
panache | npm ERR! notsup Actual Arch: x64
panache | 
panache | npm ERR! A complete log of this run can be found in:
panache | npm ERR!     /root/.npm/_logs/2023-10-11T13_34_00_893Z-debug.log
panache exited with code 1

Looks like there is a problem with fsevents.

would you please help?
Best!

@flegeai flegeai changed the title Unable to make Panache with docker on a debian OS. Unable to install Panache with docker on a debian OS. Oct 11, 2023
@flegeai
Copy link
Author

flegeai commented Oct 11, 2023

Apparently, the problem can be fix by removing the file package-lock.json.

@SingingMeerkat
Copy link
Contributor

Hi @flegeai ! thanks for letting me know, I had troubles in the past with package-lock.json, apparently I still have some cleaning to do.

I had some package conflicts when merging changes from the main branch into the bananaGenomeHub branch, it is most likely due to npm packages being update in one branch and not the other. package-lock.json is built automatically when installing the packages, from the package list in package.json. It is supposed to lock the versions of packages so that every dev has the exact same setup, but so far I am not quite convinced... In your case, overwriting it seems to have done the trick!

I'll let you know once I corrected it. Is everything else working as intended?

@flegeai
Copy link
Author

flegeai commented Oct 12, 2023

Thanks Eloi for your reply.
It looks like it works now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants