Include nuget.config in condo container

[jeffreypmoran]

I am hitting 401 errors when running condo run on my local machine. Based on feedback from @sjk07, this can be resolved by including a user's nuget.config file in the condo container that is created here -

condo-cli/cmd/run.go

Line 82 in 88e67fe

resp, err := cli.ContainerCreate(ctx, &container.Config{

[dmccaffery]

There are many issues with taking this approach in the CLI; meaning, using command line arguments to manipulate container internals. NuGet is not the only authenticated resource supported by condo.

Docker, NPM, Go Modules, etc. are also authenticated. There is no “good” way to support args for all of these.

The CLI running a container is a stop-gap to a rewrite of condo functionality without requiring the MSBuild dependency. At least that was the plan way back when.

I’m not a maintainer of these repositories anymore, but I thought I’d share some context.

Yes. An arg could be added to volume map the nuget config file on the local system through some form of platform discovery of the host. This will not work for all scenarios; however, and will also be difficult to handle correctly and to maintain as nuget config files are stacked and merged from project + solution + user + machine. One would have to ensure volume mapping of all of them to work correctly for all use cases.

[dmccaffery]

Another important comment: condo was never intended for local machine build. It’s intended as a ci/cd system.

;)