sdk-container-builds icon indicating copy to clipboard operation
sdk-container-builds copied to clipboard

Libraries and build tooling to create container images from .NET projects using MSBuild

Results 145 sdk-container-builds issues
Sort by recently updated
recently updated
newest added

`azd` currently requires a Dockerfile (either explicitly in the project or implicitly generated by the tooling) to create an image from an application. We should be able to integrate easily,...

Area: Integrations

@rainersigwald I know this was before the PR, but I'm not understanding this comment clearly: Is `/app` being prefixed or suffixed to the file path? I ask because if it's...

Area: Layer

Question semi-unrelated to this change: @rainersigwald any reason why GNU format was used? My assumption is that PAX was not used so that file size could be reduced, since it...

Area: Layer

One of our escape hatches for users that have a need to customize their base image with RUN commands (or any other functionality that we can't support) is to put...

Area: Task
Partner request
Area: Integrations

Add authentication for service connection in Azure DevOps

Currently most `MediaType` type things are hardcoded to Docker types, but we should be OCI compliant as well (configurably).

Area: Registries
Area: Library

I'm trying the new option to produce the docker image as a compressed archive (https://github.com/dotnet/sdk-container-builds/issues/283). In general this seems to work, however, the file seems to be a tar file,...

I was successfully creating containers with `dotnet publish /t:PublicContainer`, once my VS got updated to .NET8 SDK, the projects (still targeting .NET7) fail with. ```text C:\Program Files\dotnet\sdk\8.0.100\Containers\build\Microsoft.NET.Build.Containers.targets(37,7): error MSB4064: The...

When trying to create the container with `dotnet publish /t:PublishContainer --os linux --arch x64` I got the error below ``` Unhandled exception: System.IO.DirectoryNotFoundException: Could not find a part of the...

The current implementation unconditionally uses `-rwxr-xr-x.` and `root:root` for the application files. It would be nice to be able to: - control the umask (permission filter) - control the user/group...

Area: Task
Area: Library