'container' 검색 결과

Complete guide for Testcontainers NoSQL integration testing. Use when containerized integration testing for MongoDB or Redis. Covers MongoDB document operations, Redis five data structures, Collection Fixture pattern. Includes BSON serialization, index performance testing, data isolation strategy, and container lifecycle management. Keywords: testcontainers mongodb, testcontainers redis, mongodb integration test, redis integration test, nosql testing, MongoDbContainer, RedisContainer, IMongoDatabase, IConnectionMultiplexer, BSON serialization, BsonDocument, document model testing, cache testing, Collection Fixture

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Switch from Docker to Apple Container for macOS-native container isolation. Use when the user wants Apple Container instead of Docker, or is setting up on macOS and prefers the native runtime. Triggers on "apple container", "convert to apple container", "switch to apple container", or "use apple container".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Examine container isolation in a CTF sandbox, a controlled security challenge environment. The skill checks kernel and runtime conditions, verifies whether an exploit crosses into host context, and preserves a minimal reproducible chain with evidence.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Review container isolation settings in a CTF environment
• Check kernel exploit prerequisites
• Verify whether a trigger crosses the container boundary

Audit GitHub Codespaces startup time and spending, then identify up to three evidence-based improvements to development containers, machine sizes, prebuilds, or idle timeouts, with validation results and expected impact.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigating slow Codespaces startup
• Reviewing Codespaces spending
• Trimming unused development container components

Choose a serving container for models deployed on SageMaker. Match the model type to a compatible image, retrieve its address from the AWS catalog, and check regional availability, CPU or GPU variants, and required host settings.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Choose a container for an LLM deployment
• Select images for embeddings and rerankers
• Check regional image addresses and GPU compatibility

Create a container-in-container layout system using nested frames. Use an outer centered container with visible vertical boundary lines and corner markers. Inside, place inner containers inset from the edges, each with its own background and rounded frame. Technique: outer container defines global bounds, inner containers use padding to create inset spacing, layered frames (border + background) to separate levels, and consistent spacing between outer frame and inner blocks.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Expert knowledge for Azure Container Registry development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when configuring ACR Tasks, geo-replication, connected registries, image signing/verification, or Defender scanning, and other Azure Container Registry related development tasks. Not for Azure Container Apps (use azure-container-apps), Azure Container Instances (use azure-container-instances), Azure Kubernetes Service (AKS) (use azure-kubernetes-service), Azure Red Hat OpenShift (use azure-redhat-openshift).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when you need framework-agnostic Docker and container image guidance for Java projects - Dockerfile design, multi-stage Maven builds, jlink custom runtimes, micro runtime distributions such as Alpaquita, JVM container ergonomics, non-root execution, image metadata, .dockerignore, reproducible builds, vulnerability scanning, SBOM awareness, and production-safe container defaults. This should trigger for requests such as Review Java Dockerfile; Improve Docker image security; Add jlink runtime to a Java container; Add containerization to a Java project; Optimize Java container image size; Review Docker build reproducibility. Part of Plinth Toolkit

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for live container runtime analysis, mounted secrets, sidecars, namespaces, init containers, entrypoint drift, and route-to-container resolution. Use when the user asks why a live container differs from manifests, where a mounted secret is consumed, how a sidecar or init container changes runtime state, or which route resolves to which live container. Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Escape from Docker containers to the host system using container misconfigurations, mounted sockets, privileged mode, capabilities abuse, and kernel exploits. Use this skill when testing containerized environments for breakout vulnerabilities during penetration tests. Covers Docker socket mounting, cgroup escapes, nsenter techniques, and Kubernetes pod escapes.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Create high-quality, secure, and performance-optimized Containerfiles (Dockerfiles) following best practices for multi-architecture builds, OpenShift/Kubernetes compatibility, and BuildKit cache optimization. Use when the user wants to: (1) create a new Containerfile or Dockerfile for any project (Python, Rust, Go, Node.js, .NET, or any language), (2) containerize an application with multi-stage builds, (3) optimize an existing Containerfile for security, performance, or image size, (4) review or improve container image build practices, (5) set up BuildKit cache mounts for package managers, (6) create OpenShift-compatible container images with non-root users and arbitrary UID support, (7) write a .dockerignore file, or (8) apply OCI LABEL standards.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Diagnose devcontainer configuration problems and guide development environment setup. This skill should be used when the user asks to 'set up devcontainer', 'fix container startup', 'configure VS Code dev container', 'Codespaces setup', or has Docker development environment issues. Keywords: devcontainer, docker, VS Code, Codespaces, container, development environment, Dockerfile.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Develop Spring Boot features and fixes by writing tests before implementation. Guides unit, web, persistence, and integration testing with JUnit 5, Mockito, MockMvc, and Testcontainers, plus JaCoCo measurement of how much code tests cover.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Adding Spring Boot endpoints with tests first
• Writing regression tests for bug fixes
• Testing database persistence and retrieval

Helps build LabArchives connections for electronic lab notebooks and laboratory inventory. Guides endpoint selection, request signing for authentication, and user authorization, with local tools to inspect container files and prepare redacted request plans before remote operations.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Plan an electronic lab notebook API connection
• Check authentication for laboratory inventory requests
• Inspect an LA container file locally

Assess security in authorized cloud, container, and Kubernetes environments. Review excessive permissions, exposed resources, container isolation, and cluster access controls, then document findings with reproduction details and their impact.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing cloud permissions and public storage settings
• Assessing container isolation and escape paths
• Checking Kubernetes permissions and Secrets handling

Prepare an ASP.NET Core project to run in a Linux Docker container. Create a project-specific Dockerfile and .dockerignore, configure dependencies, ports, and environment variables, and check that the container image builds successfully.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Preparing an ASP.NET Core app for Docker
• Separating build and runtime image stages
• Configuring container dependencies and environment variables

Deploy and operate Falco to monitor running containers in Kubernetes or Docker. Choose a driver, validate detection rules, confirm alerts for suspicious activity, and forward those alerts to a central security monitoring system.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Installing Falco on a Kubernetes cluster
• Choosing a driver for the Linux environment
• Checking alerts for suspicious container activity

Diagnoses storage failures in GKE, Google's managed Kubernetes service, including stuck Pods, disk attachment errors, storage pressure, and missing volume expansion. It provides diagnostic commands and reviewable configuration patches for deployment through GitOps.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Diagnose Pods stuck in ContainerCreating
• Investigate slow disks and node storage pressure
• Find why expanded storage is missing inside a container

Write and review Apache SeaTunnel unit tests and E2E tests that check complete jobs using Testcontainers. It provides concrete rules for container setup, waiting, resource cleanup, and assertions to address intermittent failures and resource leaks.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Writing a new connector E2E test
• Reviewing a test diff before a pull request
• Fixing intermittent failures or resource leaks in tests

Azure Container Registry SDK for Python. Use for managing container images, artifacts, and repositories. Triggers: "azure-containerregistry", "ContainerRegistryClient", "container images", "docker registry", "ACR".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Expert C4 Container-level documentation specialist. Synthesizes Component-level documentation into Container-level architecture, mapping components to deployment units, documenting container interfaces as APIs, and creating container diagrams. Use when synthesizing components into deployment containers and documenting system deployment architecture.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Expert knowledge for Azure Kubernetes Service (AKS) development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when securing AKS with Entra/RBAC, configuring Fleet, GPUs or Wasm, AI/ML workloads, or Istio/KEDA autoscaling, and other Azure Kubernetes Service (AKS) related development tasks. Not for Azure Container Apps (use azure-container-apps), Azure Container Instances (use azure-container-instances), Azure Container Registry (use azure-container-registry), Azure Red Hat OpenShift (use azure-redhat-openshift).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Expert knowledge for Azure Container Instances development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, and deployment. Use when configuring ACI standby pools, static IP networking, GPU containers, secure ACR pulls, or GitHub Actions deploys, and other Azure Container Instances related development tasks. Not for Azure Container Apps (use azure-container-apps), Azure Kubernetes Service (AKS) (use azure-kubernetes-service), Azure App Service (use azure-app-service), Azure Virtual Machines (use azure-virtual-machines).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Audit container images, Dockerfiles, and Kubernetes manifests for misconfigurations, excessive privileges, exposed secrets, and runtime risks. Use when the user mentions 'container security,' 'Docker security,' 'Dockerfile audit,' 'Kubernetes security,' 'K8s security,' 'pod security,' 'container hardening,' 'kubectl audit,' 'image scanning,' 'distroless,' 'rootless containers,' 'pod security policy,' 'pod security standards,' 'PSS,' 'network policy,' 'OPA Gatekeeper,' 'Kyverno,' 'runtime security,' or needs to review container or orchestration security.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.