最適化されたマルチステージのDockerfileと.dockerignoreファイルを生成し、ASP.NET CoreプロジェクトをLinux環境向けにコンテナ化します。
- GitHubスター
- 41,038
- ファイル
- 1
- 最終コミット
- 2026年11月11日
- ライセンス
- MIT
- 許可されたツール
- —
containerize-aspnetcore skillは何をしますか
containerize-aspnetcoreはAgent Skillsです。 最適化されたマルチステージのDockerfileと.dockerignoreファイルを生成し、ASP.NET CoreプロジェクトをLinux環境向けにコンテナ化します。.
skillのSKILL.mdから生成された要約。
containerize-aspnetcore skill について
このSKILLは、アプリケーションをLinux環境へ移行する開発者向けに、ASP.NET Coreプロジェクトに最適化されたDocker構成を生成します。8.0や9.0といった特定の.NETバージョンに合わせて、マルチステージDockerfileと.dockerignoreファイルの作成を自動化します。プロジェクトの.csprojファイルを解析することで、適切なターゲットフレームワークを特定し、Debian、Alpine、Ubuntu、Chiseled、Azure Linuxなどの適切なLinuxディストリビューションを選択します。
カスタムNuGetフィード、システムパッケージ、またはネイティブライブラリなどの特定の要件を持つ.NETアプリケーションをコンテナ化する必要がある場合、エージェントはこのSKILLをロードする必要があります。このプロセスにより、パッケージの復元、アプリケーションのパブリッシュ、およびランタイム設定を処理する完全なビルド環境が構築されます。また、$APP_UID変数による非ルートユーザーの設定や、curlまたはwgetを使用したヘルスチェック命令の設定を通じて、セキュリティとパフォーマンスも管理します。最後に、docker buildコマンドを実行してセットアップを検証し、生成されたイメージが正常に動作することを確認します。
エージェントができること
- 1Linux用Dockerfileの作成特定のLinuxディストリビューションをターゲットとしたASP.NET Coreプロジェクト用のマルチステージDockerfileを生成します。
- 2プロジェクトの除外設定binやobjフォルダなどの不要なファイルがイメージに含まれないよう、.dockerignoreファイルをセットアップします。
- 3ヘルスモニタリングの実装特定のURLパスとインターバルを使用して、コンテナにヘルスチェック命令を追加します。
- 4プライベート依存関係の管理認証を伴うプライベートなNuGetパッケージソースを使用するようにビルドステージを構成します。
skill の SKILL.md から作成されています。すべてのユースケースは、その引用と照合されています。
containerize-aspnetcore skillのインストール方法
各コマンドはskillフォルダをクライアントのskillsディレクトリにコピーします。読み込むには、クライアントを再起動するか新しいセッションを開始してください。Claude Codeにcontainerize-aspnetcore skillをインストールする
~/.claude/skills/containerize-aspnetcore/SKILL.md
$ npx degit github/awesome-copilot/skills/containerize-aspnetcore ~/.claude/skills/containerize-aspnetcoreClaude Code (project)にcontainerize-aspnetcore skillをインストールする
.claude/skills/containerize-aspnetcore/SKILL.md
$ npx degit github/awesome-copilot/skills/containerize-aspnetcore .claude/skills/containerize-aspnetcoreCodexにcontainerize-aspnetcore skillをインストールする
~/.agents/skills/containerize-aspnetcore/SKILL.md
$ npx degit github/awesome-copilot/skills/containerize-aspnetcore ~/.agents/skills/containerize-aspnetcoreGemini CLIにcontainerize-aspnetcore skillをインストールする
~/.gemini/skills/containerize-aspnetcore/SKILL.md
$ npx degit github/awesome-copilot/skills/containerize-aspnetcore ~/.gemini/skills/containerize-aspnetcoreClaude.aiにcontainerize-aspnetcore skillをインストールする
npx degit github/awesome-copilot/skills/containerize-aspnetcore containerize-aspnetcore && zip -r containerize-aspnetcore.zip containerize-aspnetcore # claude.ai → Customize → Skills → + → Create skill → Upload a skill → containerize-aspnetcore.zip
自動チェック
実行日 2026年11月15日完全なレポート →自動チェックに合格しました。これはセキュリティ監査ではありません。エージェントに実行させる前にスクリプトを読んでください。 チェックの仕組み · 点数を上げるための改善点
- ソースリポジトリがリンクされており、アクセス可能github/awesome-copilot/skills/containerize-aspnetcore is public and reachablegithub.com/github/awesome-copilot/tree/HEAD/skills/container ↗合格
- オープンソースライセンス (OSI)MITspdx.org/licenses/MIT.html ↗合格
- 過去1年以内にコミットまたはリリースありLast commit 2026-11-11github.com/github/awesome-copilot/commits ↗合格
- スクリプトにダウンロード実行や認証情報の窃取がないNo scripts in the skill folder合格
- SKILL.md に隠れた指示がないNo override phrases, safeguard switches, credential requests or hidden charactersgithub.com/github/awesome-copilot/blob/HEAD/skills/container ↗合格
- 事前許可ツールが限定されているNo pre-approved tools; the agent asks before using onegithub.com/github/awesome-copilot/blob/HEAD/skills/container ↗合格
- SKILL.md が Agent Skills の形式に従っているthe description does not say when to use the skillgithub.com/github/awesome-copilot/blob/HEAD/skills/container ↗検出事項
SKILL.md
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))
- ✅ Proper handling of dependencies (system packages, native libraries, additional tools)
- ❌ No infrastructure setup (assumed to be handled separately)
- ❌ No code changes beyond those required for containerization
Execution Process
- Review the containerization settings above to understand the containerization requirements
- Create a
progress.mdfile to track changes with check marks - Determine the .NET version from the project's .csproj file by checking the
TargetFrameworkelement - Select the appropriate Linux container image based on:
- The .NET version detected from the project
- The Linux distribution specified in containerization settings (Alpine, Ubuntu, Chiseled, or Azure Linux (Mariner))
- If the user does not request specific base images in the containerization settings, then the base images MUST be valid mcr.microsoft.com/dotnet images with a tag as shown in the example Dockerfile, below, or in documentation
- Official Microsoft .NET images for build and runtime stages:
- SDK image tags (for build stage): https://github.com/dotnet/dotnet-docker/blob/main/README.sdk.md
- ASP.NET Core runtime image tags: https://github.com/dotnet/dotnet-docker/blob/main/README.aspnet.md
- .NET runtime image tags: https://github.com/dotnet/dotnet-docker/blob/main/README.runtime.md
- Create a Dockerfile in the root of the project directory to containerize the application
- The Dockerfile should use multiple stages:
- Build stage: Use a .NET SDK image to build the application
- Copy csproj file(s) first
- Copy NuGet.config if one exists and configure any private feeds
- Restore NuGet packages
- Then, copy the rest of the source code and build and publish the application to /app/publish
- Final stage: Use the selected .NET runtime image to run the application
- Set the working directory to /app
- Set the user as directed (by default, to a non-root user (e.g.,
$APP_UID))- Unless directed otherwise in containerization settings, a new user does not need to be created. Use the
$APP_UIDvariable to specify the user account.
- Unless directed otherwise in containerization settings, a new user does not need to be created. Use the
- Copy the published output from the build stage to the final image
- Build stage: Use a .NET SDK image to build the application
- Be sure to consider all requirements in the containerization settings:
- .NET version and Linux distribution
- Exposed ports
- User account for container
- ASPNETCORE_URLS configuration
- System package installation
- Native library dependencies
- Additional .NET tools
- Environment variables
- File/directory copying
- Volume mount points
- Health check configuration
- The Dockerfile should use multiple stages:
- Create a
.dockerignorefile in the root of the project directory to exclude unnecessary files from the Docker image. The.dockerignorefile MUST include at least the following elements as well as additional patterns as specified in the containerization settings:- bin/
- obj/
- .dockerignore
- Dockerfile
- .git/
- .github/
- .vs/
- .vscode/
- **/node_modules/
- *.user
- *.suo
- **/.DS_Store
- **/Thumbs.db
- Any additional patterns specified in the containerization settings
- Configure health checks if specified in the containerization settings:
- Add HEALTHCHECK instruction to Dockerfile if health check endpoint is provided
- Use curl or wget to check the health endpoint
- Mark tasks as completed: [ ] → [✓]
- Continue until all tasks are complete and Docker build succeeds
Build and Runtime Verification
Confirm that Docker build succeeds once the Dockerfile is completed. Use the following command to build the Docker image:
docker build -t aspnetcore-app:latest .
If the build fails, review the error messages and make necessary adjustments to the Dockerfile or project configuration. Report success/failure.
Progress Tracking
Maintain a progress.md file with the following structure:
# Containerization Progress
## Environment Detection
- [ ] .NET version detection (version: ___)
- [ ] Linux distribution selection (distribution: ___)
## Configuration Changes
- [ ] Application configuration verification for environment variable support
- [ ] NuGet package source configuration (if applicable)
## Containerization
- [ ] Dockerfile creation
- [ ] .dockerignore file creation
- [ ] Build stage created with SDK image
- [ ] csproj file(s) copied for package restore
- [ ] NuGet.config copied if applicable
- [ ] Runtime stage created with runtime image
- [ ] Non-root user configuration
- [ ] Dependency handling (system packages, native libraries, tools, etc.)
- [ ] Health check configuration (if applicable)
- [ ] Special requirements implementation
## Verification
- [ ] Review containerization settings and make sure that all requirements are met
- [ ] Docker build success
Do not pause for confirmation between steps. Continue methodically until the application has been containerized and Docker build succeeds.
YOU ARE NOT DONE UNTIL ALL CHECKBOXES ARE MARKED! This includes building the Docker image successfully and addressing any issues that arise during the build process.
Example Dockerfile
An example Dockerfile for an ASP.NET Core (.NET) application using a Linux base image.
# ============================================================
# Stage 1: Build and publish the application
# ============================================================
# Base Image - Select the appropriate .NET SDK version and Linux distribution
# Possible tags include:
# - 8.0-bookworm-slim (Debian 12)
# - 8.0-noble (Ubuntu 24.04)
# - 8.0-alpine (Alpine Linux)
# - 9.0-bookworm-slim (Debian 12)
# - 9.0-noble (Ubuntu 24.04)
# - 9.0-alpine (Alpine Linux)
# Uses the .NET SDK image for building the application
FROM mcr.microsoft.com/dotnet/sdk:8.0-bookworm-slim AS build
ARG BUILD_CONFIGURATION=Release
WORKDIR /src
# Copy project files first for better caching
COPY ["YourProject/YourProject.csproj", "YourProject/"]
COPY ["YourOtherProject/YourOtherProject.csproj", "YourOtherProject/"]
# Copy NuGet configuration if it exists
COPY ["NuGet.config", "."]
# Restore NuGet packages
RUN dotnet restore "YourProject/YourProject.csproj"
# Copy source code
COPY . .
# Perform custom pre-build steps here, if needed
# RUN echo "Running pre-build steps..."
# Build and publish the application
WORKDIR "/src/YourProject"
RUN dotnet build "YourProject.csproj" -c $BUILD_CONFIGURATION -o /app/build
# Publish the application
RUN dotnet publish "YourProject.csproj" -c $BUILD_CONFIGURATION -o /app/publish /p:UseAppHost=false
# Perform custom post-build steps here, if needed
# RUN echo "Running post-build steps..."
# ============================================================
# Stage 2: Final runtime image
# ============================================================
# Base Image - Select the appropriate .NET runtime version and Linux distribution
# Possible tags include:
# - 8.0-bookworm-slim (Debian 12)
# - 8.0-noble (Ubuntu 24.04)
# - 8.0-alpine (Alpine Linux)
# - 8.0-noble-chiseled (Ubuntu 24.04 Chiseled)
# - 8.0-azurelinux3.0 (Azure Linux)
# - 9.0-bookworm-slim (Debian 12)
# - 9.0-noble (Ubuntu 24.04)
# - 9.0-alpine (Alpine Linux)
# - 9.0-noble-chiseled (Ubuntu 24.04 Chiseled)
# - 9.0-azurelinux3.0 (Azure Linux)
# Uses the .NET runtime image for running the application
FROM mcr.microsoft.com/dotnet/aspnet:8.0-bookworm-slim AS final
# Install system packages if needed (uncomment and modify as needed)
# RUN apt-get update && apt-get install -y \
# curl \
# wget \
# ca-certificates \
# libgdiplus \
# && rm -rf /var/lib/apt/lists/*
# Install additional .NET tools if needed (uncomment and modify as needed)
# RUN dotnet tool install --global dotnet-ef --version 8.0.0
# ENV PATH="$PATH:/root/.dotnet/tools"
WORKDIR /app
# Copy published application from build stage
COPY --from=build /app/publish .
# Copy additional files if needed (uncomment and modify as needed)
# COPY ./config/appsettings.Production.json .
# COPY ./certificates/ ./certificates/
# Set environment variables
ENV ASPNETCORE_ENVIRONMENT=Production
ENV ASPNETCORE_URLS=http://+:8080
# Add custom environment variables if needed (uncomment and modify as needed)
# ENV CONNECTIONSTRINGS__DEFAULTCONNECTION="your-connection-string"
# ENV FEATURE_FLAG_ENABLED=true
# Configure SSL/TLS certificates if needed (uncomment and modify as needed)
# ENV ASPNETCORE_Kestrel__Certificates__Default__Path=/app/certificates/app.pfx
# ENV ASPNETCORE_Kestrel__Certificates__Default__Password=your_password
# Expose the port the application listens on
EXPOSE 8080
# EXPOSE 8081 # Uncomment if using HTTPS
# Install curl for health checks if not already present
RUN apt-get update && apt-get install -y curl && rm -rf /var/lib/apt/lists/*
# Configure health check
HEALTHCHECK --interval=30s --timeout=3s --start-period=5s --retries=3 \
CMD curl -f http://localhost:8080/health || exit 1
# Create volumes for persistent data if needed (uncomment and modify as needed)
# VOLUME ["/app/data", "/app/logs"]
# Switch to non-root user for security
USER $APP_UID
# Set the entry point for the application
ENTRYPOINT ["dotnet", "YourProject.dll"]
Adapting this Example
Note: Customize this template based on the specific requirements in containerization settings.
When adapting this example Dockerfile:
- Replace
YourProject.csproj,YourProject.dll, etc. with your actual project names - Adjust the .NET version and Linux distribution as needed
- Modify the dependency installation steps based on your requirements and remove any unnecessary ones
- Configure environment variables specific to your application
- Add or remove stages as needed for your specific workflow
- Update the health check endpoint to match your application's health check route
Linux Distribution Variations
Alpine Linux
For smaller image sizes, you can use Alpine Linux:
FROM mcr.microsoft.com/dotnet/sdk:8.0-alpine AS build
# ... build steps ...
FROM mcr.microsoft.com/dotnet/aspnet:8.0-alpine AS final
# Install packages using apk
RUN apk update && apk add --no-cache curl ca-certificates
Ubuntu Chiseled
For minimal attack surface, consider using chiseled images:
FROM mcr.microsoft.com/dotnet/aspnet:8.0-jammy-chiseled AS final
# Note: Chiseled images have minimal packages, so you may need to use a different base for additional dependencies
Azure Linux (Mariner)
For Azure-optimized containers:
FROM mcr.microsoft.com/dotnet/aspnet:8.0-azurelinux3.0 AS final
# Install packages using tdnf
RUN tdnf update -y && tdnf install -y curl ca-certificates && tdnf clean all
Notes on Stage Naming
- The
AS stage-namesyntax gives each stage a name - Use
--from=stage-nameto copy files from a previous stage - You can have multiple intermediate stages that aren't used in the final image
- The
finalstage is the one that becomes the final container image
Security Best Practices
- Always run as a non-root user in production
- Use specific image tags instead of
latest - Minimize the number of installed packages
- Keep base images updated
- Use multi-stage builds to exclude build dependencies from the final image
このスキルのファイル
1containerize-aspnetcore skillに関する質問
Claude Codeにcontainerize-aspnetcore skillをインストールするには
npx degit github/awesome-copilot/skills/containerize-aspnetcore ~/.claude/skills/containerize-aspnetcoreを実行してください。Claude Codeは~/.claude/skills(すべてのプロジェクト)または.claude/skills(単一プロジェクト)からskillsを読み込み、説明がタスクに一致する場合にskillを使用します。
containerize-aspnetcore skillはどのクライアントで使用できますか
Agent Skills形式を読み込むすべてのクライアントで使用できます: Claude Code、Codex、Gemini CLI、claude.ai(ZIPとしてアップロード)。skill内のスクリプトは、クライアントがコード実行を許可した場合にのみ実行されます。
コンテナにはどのLinuxディストリビューションを使用できますか?
debian、alpine、ubuntu、chiseled、またはAzure Linux (mariner) をサポートしています。
このSKILLはインフラストラクチャのセットアップも行いますか?
いいえ、このSKILLはアプリケーションの設定とDockerfileの作成に特化しており、インフラストラクチャは別途管理されていることを前提としています。
Dockerfileの作成プロセスには何が含まれますか?
ビルド用の.NET SDKイメージと、最終ステージ用の.NET runtimeイメージを使用したマルチステージDockerfileを作成します。