sdk-container-builds
sdk-container-builds copied to clipboard
dotnet
Libraries and build tooling to create container images from .NET projects using MSBuild
> I think it's reasonable that the `PublishContainer` task should output the full name of the generated container image as well, so I'll log an issue for that. _Originally posted...
For automating builds and deploys it would be useful if we can specify container environment variables via the command line. Such as: `dotnet publish --os linux --arch x64 -p:ContainerEnvironmentVariable=EnvironmentVariable=Value /t:PublishContainer...
Today the .NET CLI collects telemetry during a given build from a variety of data sources, and one part of this telemetry is the `PublishProtocol` MSBuild Property. We (MS) use...
How would i run the following docker command before the ENTRYPOINT using the SDK Container Building Tools? But this is to basically set the image to use TLS v1.2 or...
https://github.com/dotnet/dotnet-docker/pull/5241 It seems reasonable to default to these for .NET 9 Linux RIDs. The main question to me is: Is there a point at which we should ever default .NET...
I am attempting to publish my images to a local (LAN, not same device) registry during build via the following publish command: ``` dotnet publish --os linux --arch x64 -c...
Right now there are roughly two steps to container creation: * determine metadata properties for the image/basic validation (ParseContainerProperties target) * image creation (PublishContainer target) As a result, repeat publishes...
I'm looking for the equivalent of ```Dockerfile VOLUME /app/output ``` in the csproj If this is already supported today, it should be documented [here](https://learn.microsoft.com/en-us/dotnet/core/docker/publish-as-container?pivots=dotnet-8-0)
When adding the `ContainerRegistry` property to a project, and specifying a remote registry, it seems the default behaviour is that the built image will also be immediately pushed to that...
