Here are the steps that I think need to happen:

Merge When in hosted mode do not enforce localhost #321, so that in docker we can run in hosted mode and external hosts can connect to the running process
Do a new release of the tool so that we can consume it from docker image in cdpx.
In cdpx update the base image to use the 3.0 sdk which will be needed for the tool, the latest one right now is mcr.microsoft.com/dotnet/core/sdk:3.0.100-preview6-alpine. The tags can be found here: https://hub.docker.com/_/microsoft-dotnet-core-nightly-sdk

This step would also need validation. I was thinking of validating it by running the orchestrator locally and running the docker image and checking whether "Run", "Signature Help" etc work. I tried this approach and it seems like since we have "https" now , in the orchstrator there is some security validation issue where it doesnt find the connection secure or something. There is some cert that needs to be trusted somewhere. I will dig into it further.

To the best of my knowledge, the "/LocalCodeRunner/blazor-console" workspace doesn't run at the moment but that part should not be blocking for doing a release of the tool. However before we deploy the new version to production, we need to fix that issue.

Dockerfile in msazure builds should consume the dotnet try tool from myget #228

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions