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 use infisical in production .net core with infisical sdk 32bit enviroment #2913

Open
stratusaxarlis opened this issue Dec 21, 2024 · 1 comment

Comments

@stratusaxarlis
Copy link

It fails to start any project in any environent , linux , windows
in .net 9

To Reproduce

Steps to reproduce the behavior:

  1. Go to your cproj add

  2. as described in the documentation login using the following:
    ClientSettings settings = new() { SiteUrl = "https://eu.infisical.com/", Auth = new Infisical.Sdk.AuthenticationOptions { UniversalAuth = new UniversalAuthMethod { ClientId = "clientid", ClientSecret = "clientsecret } } }; var secretsClient = new InfisicalClient(settings);

  3. build for production

  4. deploy in any server
    5 You will get the following error :

  5. See error
    Unhandled exception. System.DllNotFoundException: Unable to load DLL 'infisical_c' or one of its dependencies: The specified module could not be found. (0x8007007E)
    at Infisical.Sdk.InfisicalLibrary.init(String settings)
    at Infisical.Sdk.InfisicalLibrary.Init(String settings)
    at Infisical.Sdk.InfisicalClient..ctor(ClientSettings settings)

Expected behavior

it should work in publish release but it doesnt it copies the dll in the project folder but it cannot reference it as it seems

Platform you are having the issue on:

windows server , windows 11, any OS

Additional context

Add any other context about the problem here.

@stratusaxarlis stratusaxarlis changed the title Unable to use infisical in production .net core with infisical sdk Unable to use infisical in production .net core with infisical sdk 32bit enviroment Dec 21, 2024
@Albatz6
Copy link

Albatz6 commented Jan 5, 2025

I'm currently facing the same error when trying to deploy an app using Docker on arm64 and it looks like switching to a non-arm64 image inside Dockerfile helps.

There's also a very similar issue in the sdk repo here.

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