containerize-aspnetcore
Has your agent containerize ASP.NET Core projects. It generates custom Docker files for your project.
What it does
This tool creates the necessary instructions (called Dockerfile) to turn your ASP.NET Core project into a 'container'. A container is like an isolated package that holds everything your application needs to run, making it easier to deploy in different environments.
When to use it
- ✓When you want to run your ASP.NET Core application on a server without installing everything manually.
- ✓When preparing your application for cloud deployment (like Azure, AWS, Google Cloud).
- ✓If you need to ensure your application works the same way on any computer.
Example of what to ask your AI
“Create a container for my ASP.NET Core project in the folder 'my-project/my-app.csproj', using .NET 8 and the Alpine Linux distribution.”
Want more? Open the sections below.
How to use
The easiest way: copy the message below and paste it into Claude, ChatGPT, Cursor or any AI. It reads the skill and follows the instructions.
Skill link
Ready-to-paste message
How it works
The tool analyzes the settings you provide, such as the .NET version and the desired Linux type. Based on this, it generates a file named Dockerfile, which is a step-by-step guide to building your application's container.
Installation
Easiest way: copy the skill link and paste it into Claude, ChatGPT or Cursor asking it to follow the instructions.
In the terminal (Claude Code, Codex, Cursor), in your project folder:
npx skills add github/awesome-copilot --skill containerize-aspnetcoreOr download just the file:
curl -L https://raw.githubusercontent.com/github/awesome-copilot/main/skills/containerize-aspnetcore/SKILL.md -o SKILL.mdTechnical content (original SKILL.md)
Original text by the author, straight from GitHub.
ASP.NET Core Docker Containerization Prompt
Containerization Request
Containerize the ASP.NET Core (.NET) project specified in the settings below, focusing exclusively on changes required for the application to run in a Linux Docker container. Containerization should consider all settings specified here.
Abide by best practices for containerizing .NET Core applications, ensuring that the container is optimized for performance, security, and maintainability.
Containerization Settings
This section of the prompt contains the specific settings and configurations required for containerizing the ASP.NET Core application. Prior to running this prompt, ensure that the settings are filled out with the necessary information. Note that in many cases, only the first few settings are required. Later settings can be left as defaults if they do not apply to the project being containerized.
Any settings that are not specified will be set to default values. The default values are provided in [square brackets].
Basic Project Information
Project to containerize:
[ProjectName (provide path to .csproj file)]
.NET version to use:
[8.0 or 9.0 (Default 8.0)]
Linux distribution to use:
[debian, alpine, ubuntu, chiseled, or Azure Linux (mariner) (Default debian)]
Custom base image for the build stage of the Docker image ("None" to use standard Microsoft base image):
[Specify base image to use for build stage (Default None)]
Custom base image for the run stage of the Docker image ("None" to use standard Microsoft base image):
[Specify base image to use for run stage (Default None)]
Container Configuration
Ports that must be exposed in the container image:
- Primary HTTP port:
[e.g., 8080] - Additional ports:
[List any additional ports, or "None"]
- Primary HTTP port:
User account the container should run as:
[User account, or default to "$APP_UID"]
Application URL configuration:
[Specify ASPNETCORE_URLS, or default to "http://+:8080"]
Build configuration
Custom build steps that must be performed before building the container image:
[List any specific build steps, or "None"]
Custom build steps that must be performed after building the container image:
[List any specific build steps, or "None"]
NuGet package sources that must be configured:
[List any private NuGet feeds with authentication details, or "None"]
Dependencies
System packages that must be installed in the container image:
[Package names for the chosen Linux distribution, or "None"]
Native libraries that must be copied to the container image:
[Library names and paths, or "None"]
Additional .NET tools that must be installed:
[Tool names and versions, or "None"]
System Configuration
- Environment variables that must be set in the container image:
[Variable names and values, or "Use defaults"]
File System
Files/directories that need to be copied to the container image:
[Paths relative to project root, or "None"]- Target location in container:
[Container paths, or "Not applicable"]
Files/directories to exclude from containerization:
[Paths to exclude, or "None"]
Volume mount points that should be configured:
[Volume paths for persistent data, or "None"]
.dockerignore Configuration
- Patterns to include in the
.dockerignorefile (.dockerignore will already have common defaults; these are additional patterns):- Additional patterns:
[List any additional patterns, or "None"]
- Additional patterns:
Health Check Configuration
Health check endpoint:
[Health check URL path, or "None"]
Health check interval and timeout:
[Interval and timeout values, or "Use defaults"]
Additional Instructions
Other instructions that must be followed to containerize the project:
[Specific requirements, or "None"]
Known issues to address:
[Describe any known issues, or "None"]
Scope
- ✅ App configuration modification to ensure application settings and connection strings can be read from environment variables
- ✅ Dockerfile creation and configuration for an ASP.NET Core application
- ✅ Specifying multiple stages in the Dockerfile to build/publish the application and copy the output to the final image
- ✅ Configuration of Linux container platform compatibility (Alpine, Ubuntu, Chiseled, or Azure Linux (Mariner))
…
FAQ
What is a container?
Think of a container as a standardized box that includes your application and everything it needs to function (code, libraries, settings). This ensures it runs consistently anywhere.
What is a Dockerfile?
It's a text file with instructions that Docker (the container technology) follows to build your container image. It's like a recipe for creating your application's package.
Do I need to know a lot about Docker to use this?
No. This tool abstracts the complexity, allowing you to create the container by simply specifying your project's basic settings.
Details
Original description by the author
Containerize an ASP.NET Core project by creating Dockerfile and .dockerfile files customized for the project.
repo: github/awesome-copilot
Popularity
- GitHub stars
- 40k
- Ranking position
- #5060
- License
- MIT
- Updated
- 10/15/2026
Comments
- …
More skills from this repository
acquire-codebase-knowledge
Helps your agent understand and document an existing code project. It's useful for onboarding new people or getting an overview of the architecture.
github/awesome-copilot
acreadiness-assess
Enables your agent to assess a project's readiness for AI and generate a report. It's useful for understanding how well a project is prepared to use AI tools.
github/awesome-copilot
acreadiness-generate-instructions
Helps your agent create instructions for AI tools based on an assessment. It's useful for improving how AI interacts with code and closing identified gaps.
github/awesome-copilot
acreadiness-policy
Enables your agent to help define or apply policies for AI project assessment. It's useful for standardizing how projects are evaluated and ensuring compliance.
github/awesome-copilot
Similar skills
bun-runtime
Has your agent use Bun to run, organize, and test code. It helps choose Bun over other tools and migrate existing projects.
affaan-m/ECC
database-migrations
Helps your agent make safe changes to databases. It ensures changes can be undone and minimizes downtime.
affaan-m/ECC
deployment-patterns
Sets up deployment and CI/CD workflows, containerization, and rollback strategies to ensure safe releases.
affaan-m/ECC