You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
To run inspector you need to have node installed and run it using npx. This might not be ideal in some situations, and having it available as a Docker image that you can run would allow for an alternative way to launch it, especially on Windows where configuring the environment variables it's as clean as on Linux.
Describe the solution you'd like
For a container image, the environment variables can be passed to docker run, as well as the endpoint to connect to. This does have a slightly higher level of complexity if you want to use stdio as the transport layer, but you could always solve that by mounting a volume. It might make sense to have runtimes like Python and Node in the container image as well.
Describe alternatives you've considered
I could publish/maintain my owner container image, but having it provided via the official repo would be better for the broader community.
Additional context
Ultimately, I'm wanting to integrate it with .NET Aspire as an integration, and while it can be done using npx, a container image would be a more preferred approach.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
To run inspector you need to have node installed and run it using
npx
. This might not be ideal in some situations, and having it available as a Docker image that you can run would allow for an alternative way to launch it, especially on Windows where configuring the environment variables it's as clean as on Linux.Describe the solution you'd like
For a container image, the environment variables can be passed to
docker run
, as well as the endpoint to connect to. This does have a slightly higher level of complexity if you want to usestdio
as the transport layer, but you could always solve that by mounting a volume. It might make sense to have runtimes like Python and Node in the container image as well.Describe alternatives you've considered
I could publish/maintain my owner container image, but having it provided via the official repo would be better for the broader community.
Additional context
Ultimately, I'm wanting to integrate it with .NET Aspire as an integration, and while it can be done using
npx
, a container image would be a more preferred approach.The text was updated successfully, but these errors were encountered: