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

DotNet 5.1 #387

Open
CentralizedSky opened this issue Sep 25, 2023 · 5 comments
Open

DotNet 5.1 #387

CentralizedSky opened this issue Sep 25, 2023 · 5 comments

Comments

@CentralizedSky
Copy link

Hello,

I’m currently facing a challenge while trying to run Covenant C2 on my computer. Covenant is a powerful tool, and I’ve followed the installation steps carefully. I’ve successfully installed .NET Core 3.1 and resolved previous issues related to OpenSSL and other dependencies, which were crucial for setting up Covenant.

However, when I attempt to run Covenant using the ‘dotnet run’ command, I encounter an error related to an element called ‘ICU.’ This error message prevents Covenant from running as expected. My investigations so far suggest that my system might be missing the required ICU library or that there might be an issue with my configuration.

I’ve already checked my environment variables, such as ‘LD_LIBRARY_PATH,’ to ensure they’re correctly set to locate the necessary libraries. Despite my best efforts, I haven’t been able to resolve this ICU-related problem.

If you have experience with running Covenant C2 or troubleshooting issues with similar software, I would greatly appreciate your guidance and expertise in getting this tool up and running smoothly. Covenant is essential for my work, and I’m eager to overcome this hurdle.

Thank you for any assistance you can provide.

@CentralizedSky
Copy link
Author

Uploading IMG_3374.jpeg…

@khraoverflow
Copy link

probably unpopular opinion , but working with docker is superior, 'cause it dodges stuff exactly like this, try that u won't regret it.

@CentralizedSky
Copy link
Author

About docker will it not use too much ram, that why I wasn't using it, and if I close the docker will it stop using the ram, last time I used it I had very bad experience.

@khraoverflow
Copy link

About docker will it not use too much ram, that why I wasn't using it, and if I close the docker will it stop using the ram, last time I used it I had very bad experience.

sorry for late reply , but yes when u close the container it should release the ram used, ... why what happened when u tried it ?

@CentralizedSky
Copy link
Author

About docker will it not use too much ram, that why I wasn't using it, and if I close the docker will it stop using the ram, last time I used it I had very bad experience.

sorry for late reply , but yes when u close the container it should release the ram used, ... why what happened when u tried it ?

Well! Because of you I got in docker. And it is my new favorite thing 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