New Linux Distro Version - Alpine 3.14

[mthalman]

New Linux Distro Version

Distro: Alpine 3.14

ImageBuilder Tasks

• Ensure that the ImageBuilder supports the new distro version in the code to generate the correct README display name from the version specified in the manifest

Nightly Branch Tasks

1. • Copy the Dockerfiles of the most recent version of that distro (or author new ones for an entirely new distro) and place them in a version-specific folder under their respective variants (runtime-deps, runtime, aspnet, sdk). Note: not all variants have a corresponding runtime-deps image.
2. • Modify the Dockerfiles as appropriate for any specific changes related to the new distro version
3. • Update manifest.json to reference the new set of Dockerfiles with the appropriate tags
     • Move any distro-specific floating tags to the newer version (e.g. 3.1-alpine)
4. • Update the test data to include the new distro version
5. • Update the tags metadata templates to include the new distro version
6. • Run the command to update the READMEs: .\eng\readme-templates\Get-GeneratedReadmes.ps1
7. • Run the command to update the image size baseline file: .\tests\performance\Validate-ImageSize.ps1 -UpdateBaselines
8. • Inspect generated changes for correctness
9. • Consider whether sample Dockerfiles should be authored if this is a new distro and them to the samples
10. • Run the command to build and test your changes: .build-and-test.ps1 -OS <os>
11. • Commit generated changes
12. • Create PR
13. • Get PR signoff
14. • Merge PR to nightly branch
15. • Wait for automatically queued CI build to finish on dotnet-docker-nightly pipeline (internal MSFT link)
16. • Confirm READMEs have been updated in Docker Hub

Main Branch Tasks

1. • After the product teams have signed off on the new distro, merge these changes to the main branch as part of the release process for the next .NET release
2. • Create an announcement (example: Alpine 3.10) unless the new distro is added only for pre-release versions in which the announcement would be incorporated in the pre-release notes.

Related to dotnet/core#6375

[AshDerTest]

Hi

With regards to 3.14 - Apline, will this now be updated to 3.14.1 due to the security vulnerability picked up in the distro. (issue: https://security.alpinelinux.org/vuln/CVE-2021-36159)

[mthalman]

It already is updated to 3.14.1:

❯ docker pull mcr.microsoft.com/dotnet/nightly/aspnet:5.0-alpine3.14
5.0-alpine3.14: Pulling from dotnet/nightly/aspnet
Digest: sha256:75af56e6110610b5b6483789f43d5d6e1363ac64609010600c9d1ce0e2b3c7ae
Status: Downloaded newer image for mcr.microsoft.com/dotnet/nightly/aspnet:5.0-alpine3.14
mcr.microsoft.com/dotnet/nightly/aspnet:5.0-alpine3.14

❯ docker run --rm mcr.microsoft.com/dotnet/nightly/aspnet:5.0-alpine3.14 cat /etc/os-release
NAME="Alpine Linux"
ID=alpine
VERSION_ID=3.14.1
PRETTY_NAME="Alpine Linux v3.14"
HOME_URL="https://alpinelinux.org/"
BUG_REPORT_URL="https://bugs.alpinelinux.org/"

[ashinde90]

When should we expect an update to manifest file so that the Dockerfile can be used efficiently without the manifest issue ?

[mthalman]

When should we expect an update to manifest file so that the Dockerfile can be used efficiently without the manifest issue ?

Are you asking when Alpine 3.14 will be made available from the main (official) branch instead of nightly (preview)? We're targeting the next servicing release scheduled for Sep 14.