Action-dotnet-v2.2

Docker image providing a .NET Core 2.2 runtime for building and running serverless actions in the Apache OpenWhisk platform.

  • Development
  • Tools & Utilities
Docker image providing a .NET Core 2.2 runtime for building and running serverless actions in the Apache OpenWhisk platform.

Platform availability

Available on 0 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

71/100 Good

Maintained
100last commit 18 days ago
Popular
621,222 GitHub stars
Easy to install
250 install platforms, install notes, Docker image
Light to run
No data
Security check
72no serious findings, 4 minor, CI, tests, OpenSSF Scorecard 6.5/10

Based on 4 of 5 factors.

GitHub stars
1,222
Open issues
34
Last commit
2026-11-03
Latest release
v6.1.0
License
MIT
Activity
rising

Checked 2 days ago - source: GitHub (actions/setup-dotnet)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is not supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Obtaining and deploying the image Pull the image from Docker Hub (openwhisk/action-dotnet-v2.2); it supplies the .NET Core 2.2 runtime that Apache OpenWhisk uses to schedule and run your compiled .NET actions in Docker containers in response to events. source

Fetched 15 days ago - each note links to its source

Alternatives (8)

  • BunkerWeb - BunkerWeb is a self-hosted, open-source web application firewall and NGINX-based web server that protects services with secure-by-default s…
  • Caddy - Caddy is an extensible web server and reverse proxy that serves Transport Layer Security (TLS) by default, making it simple to secure and r…
  • Corvus - Self-hosted reverse proxy and web application firewall with a web console; it provides domain forwarding, free SSL, live traffic monitoring…
  • Ferron - Ferron is a web server optimized for speed, security, and efficiency.
  • HFS 2 (HTTP File Server) - You can use HFS (HTTP File Server) to send and receive files.
  • Microsoft IIS - Internet Information Services (IIS) for Windows® Server is a flexible, secure and easy-to-manage Web server for hosting anything on the Web.
  • lighttpd - Lighttpd is a secure, lightweight web server that uses memory and CPU more efficiently than comparable servers, with FastCGI, CGI, authenti…
  • nginx - Nginx is an HTTP web server, reverse proxy, content cache, load balancer, TCP/UDP proxy, and mail proxy server.

Checked 15 days ago - source: AlternativeTo

Common questions

How do I set a specific .NET SDK version in a GitHub Actions workflow?

The setup-dotnet action is used to set up the workflow with a specific version of the .NET core SDK.

Why might a workflow display the wrong .NET version when using setup-dotnet?

setup-dotnet v4 fixed the problem by installing an LTS version of the dotnet executable and using it for subsequent dotnet installations. The first install-script only performs the actual download once per workflow.

What self-hosted agent issue can make actions/checkout fail?

A Windows 2019 self-hosted agent may fail when actions/checkout@v2 checks out the repository because it does not fully unzip the payload.

Can an old setup-dotnet workflow still compile after a long pause?

One report says an older YAML that had not been run for a year compiled without issues, though it produced a CodeQL warning that required updating from v2 to v3.

Answers sourced from github.com, github.com, stackoverflow.com, www.reddit.com

Community

Collected 48 days ago - public community threads