From #215

Right now, the EF Core commands in the plugin can be executed in two modes:

1. Explicit terminal-like console (default)
2. Silent, with notification after done

Both modes start dotnet ef execution as a child of the Rider frontend process, which means that dotnet ef inherits the environment of Rider, which may be different from the user's environment.

It is a problem in some Unix-based OSes where the user's environment may be very different from the one that Toolbox or package managers use to start Rider.

The only proper way to fix the problem from Rider's side would be to execute commands through the internal terminal infrastructure, which starts the shell process with the real user's environment and not from the Rider process.