azure-functions-dotnet-fips

packaged by Chainguard

Chainguard Container for azure-functions-dotnet-fips

FIPS-compliant Azure Functions .NET isolated worker runtime image.

Chainguard Containers are regularly-updated, secure-by-default container images.

Download this Container Image

For those with access, this container image is available on cgr.dev:

docker pull cgr.dev/ORGANIZATION/azure-functions-dotnet-fips:latest

Be sure to replace the ORGANIZATION placeholder with the name used for your organization's private repository within the Chainguard Registry.

Compatibility Notes

This image is the FIPS-compliant variant of the azure-functions-dotnet image. It uses a FIPS-validated cryptographic module and is built for workloads that require FIPS 140-2/140-3 compliance.

It is based on the .NET isolated worker model (FUNCTIONS_WORKER_RUNTIME=dotnet-isolated) and shares the same runtime behaviour as the non-FIPS variant:

• Extension Bundles: Supports only Azure Functions Extension Bundles v4.
• Worker indexing: AzureWebJobsFeatureFlags=EnableWorkerIndexing is set, matching the upstream isolated worker behaviour.

Getting Started

The .NET isolated model runs your C# function code as a separate process from the Azure Functions host, communicating over gRPC. Users build their function app with dotnet publish and deploy the output to /home/site/wwwroot inside the container.

Creating and running a minimal .NET isolated Function locally

Start by creating a .NET isolated function app. You will need the Azure Functions Core Tools and the .NET 8 SDK installed locally.

func init HelloDotnet --worker-runtime dotnet-isolated --target-framework net8.0
cd HelloDotnet
func new --name HttpTrigger --template "HTTP trigger" --authlevel "anonymous"
dotnet publish -c Release -o publish/

Add a Dockerfile to copy your published function to the Chainguard image:

cat >Dockerfile <<EOL
FROM cgr.dev/<ORGANIZATION>/azure-functions-dotnet-fips:latest

COPY publish/ /home/site/wwwroot/
EOL

Build and run the image:

docker build -t my-azure-function .
docker run -p 8080:80 \
  -e AzureWebJobsStorage="UseDevelopmentStorage=true" \
  my-azure-function

Once running, test the HTTP trigger:

curl http://127.0.0.1:8080/api/HttpTrigger
# Hello from Chainguard Azure Functions!

Deploying to Azure Function App

The most common use case is deploying the image to an Azure Function App. Publish your built image to a container registry and configure your Function App to use it. See the official documentation for full instructions.

Documentation and Resources

• official documentation.
• azure-functions-dotnet github

What are Chainguard Containers?

Chainguard's free tier of Starter container images are built with Wolfi, our minimal Linux undistro.

All other Chainguard Containers are built with Chainguard OS, Chainguard's minimal Linux operating system designed to produce container images that meet the requirements of a more secure software supply chain.

The main features of Chainguard Containers include:

• Minimal design, without unnecessary software bloat
• Daily builds to ensure container images are up-to-date with available security patches
• High quality build-time SBOMs attesting to the provenance of all artifacts within the image
• Verifiable signatures provided by Sigstore
• Reproducible builds with Cosign and apko (read more about reproducibility)

For cases where you need container images with shells and package managers to build or debug, most Chainguard Containers come paired with a development, or -dev, variant.

In all other cases, including Chainguard Containers tagged as :latest or with a specific version number, the container images include only an open-source application and its runtime dependencies. These minimal container images typically do not contain a shell or package manager.

Although the -dev container image variants have similar security features as their more minimal versions, they include additional software that is typically not necessary in production environments. We recommend using multi-stage builds to copy artifacts from the -dev variant into a more minimal production image.

Need additional packages?

To improve security, Chainguard Containers include only essential dependencies. Need more packages? Chainguard customers can use Custom Assembly to add packages, either through the Console, chainctl, or API.

To use Custom Assembly in the Chainguard Console: navigate to the image you'd like to customize in your Organization's list of images, and click on the Customize image button at the top of the page.

Learn More

Refer to our Chainguard Containers documentation on Chainguard Academy. Chainguard also offers VMs and Libraries — contact us for access.

Trademarks

This software listing is packaged by Chainguard. The trademarks set forth in this offering are owned by their respective companies, and use of them does not imply any affiliation, sponsorship, or endorsement by such companies.