[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75XCW0SWXHHXRPDES33EXBT":3,"skill-same:01M75XCW0SWXHHXRPDES33EXBT":45},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M75XCW0SWXHHXRPDES33EXBT","d9c-net-storage",null,"Networks and volumes on a d9c host — which containers share a network, why two containers cannot reach each other, which containers use a volume, and creating a network or volume. Use when someone reports connection refused or name resolution failures between containers, asks where data is stored, or needs a new network or volume.","kirg0\u002Fd9c","kirg0","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F93735124?v=4","01M75XC6PNMMV90SHG5MDMYYEF","Kirill Garanin","01M75XC6Q9SC7P2Y9XZB4P8X2M",7,"MIT","https:\u002F\u002Fgithub.com\u002Fkirg0\u002Fd9c\u002Fblob\u002Fmain\u002Fplugins\u002Fd9c\u002Fskills\u002Fd9c-net-storage\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: d9c-net-storage\ndescription: Networks and volumes on a d9c host — which containers share a network, why two containers cannot reach each other, which containers use a volume, and creating a network or volume. Use when someone reports connection refused or name resolution failures between containers, asks where data is stored, or needs a new network or volume.\n---\n\n# Networks and volumes with d9c\n\nFollow the base `d9c` skill. Listing and inspecting are **read**; creating is **safe**; removing\nvolumes goes through `d9c-cleanup` (volume prune is destructive and loses data).\n\n## Who is connected to what\n\n- `d9c networks` \u002F `d9c_resources` `{action: \"networks\"}`: name, driver, scope, subnet.\n- `d9c ps -a --fields name,state,networks,ports` \u002F `d9c_containers` `{action: \"ps\", all: true}`:\n  the networks of every container — group by network to see who can talk to whom.\n- `d9c inspect \u003Cnetwork> --type network` \u002F `d9c_containers` `{action: \"inspect\", target: \"\u003Cnetwork>\", type: \"network\"}`:\n  the attached containers with their addresses, the IPAM subnet and gateway, and `internal` (no\n  outside access).\n\n## Why can't A reach B\n\nWork through these in order and stop at the first that explains it:\n\n1. **Both running?** `d9c ps -a` — a stopped or restarting B refuses connections.\n2. **A shared network?** Compare their `networks`. Containers on different user networks cannot\n   reach each other; containers on the default `bridge` network cannot resolve each other by name\n   (only user-defined networks have DNS). Fix: connect both to one user-defined network (in\n   compose, the same `networks:` entry).\n3. **The right name and port?** Use B's container or compose service name and its container port\n   (the `80` of `0.0.0.0:8080->80\u002Ftcp`), not the published host port.\n4. **Listening?** B must listen on `0.0.0.0` inside the container, not `127.0.0.1`. Check B's logs\n   for the bind address: `d9c logs \u003CB> --grep 'listen|bind'`.\n5. **Internal or isolated network?** An `internal` network blocks traffic to the outside, not\n   between its members.\n\nTo test from inside A, `d9c exec \u003CA> -- getent hosts \u003CB>` resolves the name — exec is\ndestructive-tier, so suggest it and run it only after an explicit yes.\n\n## Volumes\n\n- `d9c volumes` \u002F `d9c_resources` `{action: \"volumes\"}`: name, driver, mount point.\n- Which containers use a volume: `d9c inspect \u003Ccontainer>` \u002F `d9c_containers` `{action: \"inspect\", target: \"\u003Ccontainer>\"}`\n  — `mounts` lists type, name, source and destination. A named volume no container mounts is a\n  cleanup candidate; report it, do not remove it.\n- `d9c inspect \u003Cvolume> --type volume` shows the driver, mount point and labels (a compose\n  project label tells which stack created it).\n\n## Create\n\n- Network: `d9c network create backend-net --subnet 172.28.0.0\u002F16` \u002F\n  `d9c_create` `{action: \"network\", name: \"backend-net\", subnet: \"172.28.0.0\u002F16\"}` (`--gateway`\n  must lie inside `--subnet`; the driver defaults to bridge).\n- Volume: `d9c volume create uploads` \u002F `d9c_create` `{action: \"volume\", name: \"uploads\"}`.\n- Preview with `--dry-run` \u002F `dry_run: true`; a name that exists fails with `usage`.\n- Attaching an existing container to a network is not available in d9c: propose the compose or\n  `docker network connect` change to the user.\n","# Networks and volumes with d9c\n\nFollow the base `d9c` skill. Listing and inspecting are **read**; creating is **safe**; removing\nvolumes goes through `d9c-cleanup` (volume prune is destructive and loses data).\n\n## Who is connected to what\n\n- `d9c networks` \u002F `d9c_resources` `{action: \"networks\"}`: name, driver, scope, subnet.\n- `d9c ps -a --fields name,state,networks,ports` \u002F `d9c_containers` `{action: \"ps\", all: true}`:\n  the networks of every container — group by network to see who can talk to whom.\n- `d9c inspect \u003Cnetwork> --type network` \u002F `d9c_containers` `{action: \"inspect\", target: \"\u003Cnetwork>\", type: \"network\"}`:\n  the attached containers with their addresses, the IPAM subnet and gateway, and `internal` (no\n  outside access).\n\n## Why can't A reach B\n\nWork through these in order and stop at the first that explains it:\n\n1. **Both running?** `d9c ps -a` — a stopped or restarting B refuses connections.\n2. **A shared network?** Compare their `networks`. Containers on different user networks cannot\n   reach each other; containers on the default `bridge` network cannot resolve each other by name\n   (only user-defined networks have DNS). Fix: connect both to one user-defined network (in\n   compose, the same `networks:` entry).\n3. **The right name and port?** Use B's container or compose service name and its container port\n   (the `80` of `0.0.0.0:8080->80\u002Ftcp`), not the published host port.\n4. **Listening?** B must listen on `0.0.0.0` inside the container, not `127.0.0.1`. Check B's logs\n   for the bind address: `d9c logs \u003CB> --grep 'listen|bind'`.\n5. **Internal or isolated network?** An `internal` network blocks traffic to the outside, not\n   between its members.\n\nTo test from inside A, `d9c exec \u003CA> -- getent hosts \u003CB>` resolves the name — exec is\ndestructive-tier, so suggest it and run it only after an explicit yes.\n\n## Volumes\n\n- `d9c volumes` \u002F `d9c_resources` `{action: \"volumes\"}`: name, driver, mount point.\n- Which containers use a volume: `d9c inspect \u003Ccontainer>` \u002F `d9c_containers` `{action: \"inspect\", target: \"\u003Ccontainer>\"}`\n  — `mounts` lists type, name, source and destination. A named volume no container mounts is a\n  cleanup candidate; report it, do not remove it.\n- `d9c inspect \u003Cvolume> --type volume` shows the driver, mount point and labels (a compose\n  project label tells which stack created it).\n\n## Create\n\n- Network: `d9c network create backend-net --subnet 172.28.0.0\u002F16` \u002F\n  `d9c_create` `{action: \"network\", name: \"backend-net\", subnet: \"172.28.0.0\u002F16\"}` (`--gateway`\n  must lie inside `--subnet`; the driver defaults to bridge).\n- Volume: `d9c volume create uploads` \u002F `d9c_create` `{action: \"volume\", name: \"uploads\"}`.\n- Preview with `--dry-run` \u002F `dry_run: true`; a name that exists fails with `usage`.\n- Attaching an existing container to a network is not available in d9c: propose the compose or\n  `docker network connect` change to the user.\n",{"name":5,"description":7},"main","5e185df671621a32990f8240e8462c37de262dea","plugins\u002Fd9c\u002Fskills\u002Fd9c-net-storage",0,"https:\u002F\u002Fgithub.com\u002Fkirg0\u002Fd9c","https:\u002F\u002Fgithub.com\u002Fkirg0","2026-10-28 23:21:03",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add kirg0\u002Fd9c --skill d9c-net-storage",{"tool":37,"command":38},"bunx","bunx skills add kirg0\u002Fd9c --skill d9c-net-storage",{"tool":40,"command":41},"pnpm","pnpm dlx skills add kirg0\u002Fd9c --skill d9c-net-storage","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fkirg0\u002Fd9c\u002Fblob\u002Fmain\u002Fplugins\u002Fd9c\u002Fskills\u002Fd9c-net-storage\u002FSKILL.md",true,[],[46,53,60,67,74,81],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":19},"01M75XD6SSST8RC2Z9R4CWK6HG","d9c","Base guide for managing Docker, Podman, nerdctl or CRI-O hosts through d9c — installing it, saved hosts, the JSON output contract and exit codes, the write policy and the untrusted-data rule. Use when a task involves containers, images or compose projects on a host d9c manages and no more specific d9c skill fits — read it before the first d9c command or d9c_* MCP tool call; the other d9c skills build on it.","https:\u002F\u002Fgithub.com\u002Fkirg0\u002Fd9c\u002Fblob\u002Fmain\u002Fplugins\u002Fd9c\u002Fskills\u002Fd9c\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M75XD2TKH6RAQVQ5FHN2ZFE8","d9c-troubleshoot","Diagnose a container that crashed, keeps restarting, is unhealthy or is slow, using d9c — exit codes, OOM kills, restart counts, health checks, logs and CPU\u002Fmemory. Use when someone asks why a container is down, flapping or sluggish.","https:\u002F\u002Fgithub.com\u002Fkirg0\u002Fd9c\u002Fblob\u002Fmain\u002Fplugins\u002Fd9c\u002Fskills\u002Fd9c-troubleshoot\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M75XCZKSNEDP0Q0HY4GFY5VM","d9c-security-audit","Read-only security review of the containers on a d9c host — privileged mode, root users, the engine socket mounted into containers, sensitive host paths, ports published on all interfaces, mutable latest tags, missing resource limits and secrets in environment variables. Use when someone asks whether a host or stack is configured safely or wants a container hardening report.","https:\u002F\u002Fgithub.com\u002Fkirg0\u002Fd9c\u002Fblob\u002Fmain\u002Fplugins\u002Fd9c\u002Fskills\u002Fd9c-security-audit\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M75XCSA9DFJCNHSSSC5P8VC0","d9c-logs","Investigate container and compose project logs with d9c within a token budget — time windows, regex filters, per-project merged logs and correlation with engine events. Use when the answer is somewhere in the logs, such as an error spike, a request trace or what happened at a given time.","https:\u002F\u002Fgithub.com\u002Fkirg0\u002Fd9c\u002Fblob\u002Fmain\u002Fplugins\u002Fd9c\u002Fskills\u002Fd9c-logs\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M75XCNGRA6X4CM9V5VD55X2Y","d9c-lifecycle","Start, stop, restart, kill or remove containers with d9c — by name, ID prefix or a filter such as label or image, with a dry-run plan, the user's approval for destructive steps, and a wait until the result is running or healthy. Use when someone asks to bring containers up or down, bounce a service, or delete containers.","https:\u002F\u002Fgithub.com\u002Fkirg0\u002Fd9c\u002Fblob\u002Fmain\u002Fplugins\u002Fd9c\u002Fskills\u002Fd9c-lifecycle\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M75XCJD86Q31T5DKMWDB7T1V","d9c-images","Work with container images on a d9c host — build from a local Dockerfile, tag, push to a registry, read the layer history, and find images no container uses before removing them. Use when someone asks to build, retag, publish or inspect an image, or wants to know which images are stale or unused.","https:\u002F\u002Fgithub.com\u002Fkirg0\u002Fd9c\u002Fblob\u002Fmain\u002Fplugins\u002Fd9c\u002Fskills\u002Fd9c-images\u002FSKILL.md",[],[]]