sdk-container-builds
sdk-container-builds copied to clipboard
dotnet
Libraries and build tooling to create container images from .NET projects using MSBuild
I have found https://learn.microsoft.com/en-us/dotnet/core/docker/publish-as-container?pivots=dotnet-8-0, https://github.com/dotnet/sdk-container-builds/issues/311 and https://github.com/dotnet/sdk-container-builds/issues/236, but still don't know how I can configure multiple container image tags while using a version environment variable. Using: Net 8, latest version...
To improve the quality of the SDK Containers feature and improve confidence in the rollout of the feature across MDE, we need to * audit MDE deployment methods to determine...
(I am not sure if container builds already do this) Currently, when building container images for multi-project solutions, it would be valuable to have the .NET SDK automatically create separate...
Today, you can't publish containers for a project with a list of RIDs that contains musl and non-musl Linux RID values. This is because we take the set of RIDs...
When publishing a container image through the .NET SDK Containers support "`Target:_PublishSingleContainer`, `Task:CreateNewImage`", the result returned to the caller is always SUCCESS (`True`, no excepction(s) thrown) even: - The target...
In csproj: ``` ``` Build target: ``` publish: stage: publish image: mcr.microsoft.com/dotnet/sdk:9.0 script: - dotnet publish /t:PublishContainer ``` Build output (redacted). ``` $ dotnet publish /t:PublishContainer Determining projects to restore......
Hi, I am trying to build a container from a project which requires command line args for some actions, but not by default. I.e. running `myapp` is as valid as...
Hi, Trying to use container publishing with Google container (aka Artifact) registry always fails. I've tried playing around with the env vars `DOTNET_CONTAINER_DEBUG_REGISTRY_FORCE_CHUNKED_UPLOAD` and `DOTNET_CONTAINER_REGISTRY_CHUNKED_UPLOAD_SIZE_BYTES` - neither setting changed the...
The documentation [here ](https://github.com/dotnet/sdk-container-builds/blob/58427d986ca900d11ae9862a7013e9016e60299c/docs/ContainerCustomization.md#containerruntimeidentifiers) states that the ContainerRuntimeIdentifier defaults to linux-x64. We've been relying on that functionality for over a year and it has been working great. Our CI pipelines...
`ContainerAppCommand` default value is : `dotnet $(ContainerWorkingDirectory)$(TargetFileName)`. It should be `dotnet ./$(TargetFileName)`. In windows-host-process mode, it shows /app/mydll.dll is not found. Consider following yaml: ``` yaml apiVersion: apps/v1 kind: DaemonSet...
