Saltar al contenido
Nuevo

DeepSeek V4.1 Flash gratis por 7 días: 10M tokens al día tras una recarga de $10 o más. Hasta el 30/11.

Cómo funciona
zhaoxuya520/competition-container-runtimeLinux, cloud y contenedores

competition-container-runtime

⁨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 m⁩

v2026.9.22-cab634b3 instalaciones+3 en 7 días44,8 mil EstrellasMITsincronizado hace 2 horas

Instalar

¿Aún no tienes la CLI de NotHoly? Instálala primero.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install zhaoxuya520/competition-container-runtime

Escribe en ⁦~/.notholy/skills⁩ después de comprobar la firma y el SHA-256.

FirmaFirmado, ed25519
4j+0VezNMd…3nXQXZAg==La CLI comprueba el SHA-256 y la firma antes de escribir cualquier archivo.
Paquete60fb3fac…1a740836
60fb3facb965…88211a7408363 archivos · ⁦2.1 KB⁩
EscaneoBajosin hallazgos
El escaneo no encontró nada que señalar en esta versión.Ver el escaneo completo
Fuentegithub.com/zhaoxuya520/reverse-skill/tree/main/CTF-Sandbox-Orchestrator/competition-container-runtime@cab634b

Esta entrada todavía no está escrita en tu idioma, así que aparece en English.

Use this skill only as a downstream specialization after $ctf-sandbox-orchestrator is already active and has established sandbox assumptions, node ownership, and evidence priorities. If that has not happened yet, return to $ctf-sandbox-orchestrator first.

Use this skill when the challenge is really about what the live container or pod is doing now, not what the checked-in manifest claims it should do.

Reply in Simplified Chinese unless the user explicitly requests English.

Quick Start

  1. Split intent from reality: manifest, image, startup, live mount, live route, live process.
  2. Map host -> proxy -> container or pod -> mounted volume -> consuming process.
  3. Keep secrets, rendered config, init output, and sidecar output separate from static manifests.
  4. Prove one minimal live path from mounted or injected state to reachable behavior.
  5. Reproduce the effect with the smallest runtime-specific chain.

Workflow

1. Map The Live Runtime

  • Compare compose or kube manifests against running containers, pods, mounted volumes, env, sidecars, init containers, and entrypoints.
  • Identify which process actually consumes the mounted secret, rendered config, or shared volume output.

2. Trace Route And Mount Boundaries

  • Map virtual host, reverse proxy, service, container port, filesystem mount, and runtime-generated file paths together.
  • Record whether the decisive state is image-baked, env-injected, mounted later, or written by an init/sidecar process.

3. Report The Runtime Deviation

  • State the earliest point where live runtime diverges from checked-in intent.
  • Keep one compact evidence chain from manifest or compose intent to live consumer behavior.

Read This Reference

  • Load references/container-runtime.md for the runtime checklist, mount-chain checklist, and common live-vs-static pitfalls.
  • If the hard part is kube API permissions, service-account trust, RBAC edges, admission mutations, or controller-created workload drift, prefer $competition-k8s-control-plane.
  • If the hard part is Host-header routing, path-prefix rewriting, or route-to-service mapping across nodes, prefer $competition-runtime-routing.
  • If the hard part is proving container-to-host crossover, kernel attack-surface preconditions, or stable escape primitives, prefer $competition-kernel-container-escape.
  • If the hard part is replaying Linux secrets, socket trust edges, or host-to-host pivots after container foothold, prefer $competition-linux-credential-pivot.

What To Preserve

  • Compose/Kubernetes fragments tied to live mounts or routes
  • Container IDs, pod names, mount paths, sidecar outputs, rendered config paths, and consuming processes
  • The exact route or file path that becomes reachable only at runtime

Archivos de esta versión

Permisos

PermisoDeclaradoHallado en el escaneo
Lee archivosNoNo
Escribe archivosNoNo
Ejecuta comandos de shellNoNo
Usa la redNoNo
Usa conectoresNoNo
Controla un navegadorNoNo

Hallazgos del escaneo

Revisado el 13 nov 2026

El escaneo no encontró nada que señalar en esta versión.

Un escaneo limpio baja el riesgo, pero no prueba que el paquete sea seguro. Lee lo que instalas.

VersiónPublicadaCommitSHA-256FirmaCambio de permisos
v2026.9.22-cab634b13 nov 2026cab634b60fb3facFirmada–

Pregunta todo lo que tu alcance permite.

Crea la cuenta, añade créditos y haz la primera pregunta en el chat o en la terminal.

  1. 1/3

    Crea la cuenta

    Individual o empresa. Puedes pasar a empresa después sin perder saldo ni claves.

    IndividualEmpresa
  2. 2/3

    Añade créditos

    Con tarjeta. Pagas por token, sin suscripción.

    $5.00recarga mínima
  3. 3/3

    Pregunta

    En el chat, o instala el CLI y ejecuta notholy login en tu terminal.

    $ notholy login