-
Notifications
You must be signed in to change notification settings - Fork 175
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 Cuckoo on Redhat OS #509
Comments
Hi @HNT3R , I have to create an environment with cuckoo on Redhat os. Would you be so kind and share your install steps with me? I got the same error during my install steps, this package solved that: Thanks, |
@C1ph3R-s thanks m8 for your response unfortunately this did not resolve the issue, would you like to share the steps for dependencies installation since I had to look for alternative in RH packages ? |
@HNT3R Sure, I have created a
|
Thanks for sharing the step, I have followed the same over docker and ver user same it does not execute. appreciate your support m8 |
@HNT3R I don't know your env, but this file still working on my container.
|
Virtualenv as mentioned on Cuckoo documentation in below link. $ virtualenv venv https://cuckoo.readthedocs.io/en/latest/installation/host/installation/#create-a-user |
@HNT3R I see but how do you mean |
I followed the steps and got same error as in my first post, also it seems the docker package is not available from the Red Hat repositories which is replaced by container-tools module, have you tested it on Redhat 8? best regards |
@HNT3R I have tested it on centos7 ans 8. |
I had this problem on Ubuntu 18.04 LTS, |
Dears,
I'm facing issue while installing Cuckoo on Redhat 8.4, after completing the requirements from documentation once I run the command to install it keep showing this error :
Command "python setup.py egg_info" failed with error code 1 in /tmp/pip-build-4SFC85/jsonschema/
and I have checked that setuptools is already installed and jsonschema also.
Any idea how to fix this issue ?
thanks ~
The text was updated successfully, but these errors were encountered: