docker-tools
docker-tools copied to clipboard
dotnet
This is a repo to house some common tools for our various docker repos.
This tracks the https://github.com/microsoft/mcr/issues/686 (internal MSFT link) issue for providing vulnerability scan results of published images to customers.
AzDO now supports the selection of which stages should be run when queuing a build. In theory, this would mean the [`stages` variable](https://github.com/dotnet/docker-tools/blob/f5dc3c6f4bc8ad430fe4faae000dfd77fdd04927/eng/common/templates/stages/build-test-publish-repo.yml#L23) could be obsolete. This should be investigated...
Enabling nullable reference types by default for the project can help guard against dereferencing null objects. See https://docs.microsoft.com/en-us/dotnet/csharp/nullable-references
There is becoming a fair amount of logic defined within the ImageBuilder tool that could be shared elsewhere. Examples include: [FilePusher](https://github.com/dotnet/docker-tools/tree/master/eng/file-pusher), Docker repo unit tests (DockerHelper). This shared logic could...
The [FilePusher](https://github.com/dotnet/docker-tools/tree/master/eng/file-pusher) utility will not handle removing any deleted files from the eng/common folder when creating PRs to push the infra to the consuming repos.
Now that we have unit tests for the ImageBuilder solution, the build pipeline should publish the test results so the results can be easily consumed in the pipeline UI.
Currently the Nano Server Docker image doesn't support running image-builder within the container. The goal is to be able to do the following `docker run -it --rm -v \\.\pipe\docker_engine:\\.\pipe\docker_engine mcr.microsoft.com/dotnet-buildtools/image-builder:nanoserver-...
The names of the variables emitted by ImageBuilder are very generic like "osType", "osVersion", and "architecture". When these variables are referenced in the pipelines, it is not obvious to know...
With the following Dockerfile, the parsing logic incorrectly detects `SOURCE` as an external dependency and tries to pull it when building. ``` FROM microsoft/dotnet-buildtools-prereqs:alpine-3.6 RUN apk update ENV NODE_VERSION 10.13.0...
Part of #1264 I haven't tested this in-place yet since it only runs on real builds, so marking as a draft for now. Early next week I'll run a test...
