Skip to content
Back to skills

Docker Sandbox

BSecurity

Docker sandbox environment management for dotfiles. Use when user mentions "build docker", "start container", "enter shell", "clean container", "check status", "make build", "make shell", "make clean", development environment, or container management.

  • 666 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added February 8, 2026
toolspythonshellbashnodedocker

Security analysis

B88/100
  • criticalModifies startup scripts or system services for persistence

Pro shows the line behind each finding and how to fix it

Scanned February 12, 2026

npx -y skills add majiayu000/claude-skill-registry --skill docker-sandbox --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Docker Sandbox?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Docker Sandbox
[![Security: B — Skills Directory](https://www.skillsdirectory.com/api/skills/majiayu000-docker-sandbox/badge)](https://www.skillsdirectory.com/skills/majiayu000-docker-sandbox)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: docker-sandbox
description: Docker sandbox environment management for dotfiles. Use when user mentions "build docker", "start container", "enter shell", "clean container", "check status", "make build", "make shell", "make clean", development environment, or container management.
---

# Docker Sandbox Management

dotfilesをテストするためのDocker開発環境を管理する。

## Available Commands

| Command | Description |
|---------|-------------|
| `make build` | Build Docker image |
| `make start` | Start container in background |
| `make shell` | Attach to container (auto-starts if needed) |
| `make run` | Run temporary container (removed after exit) |
| `make stop` | Stop container |
| `make clean` | Remove container and volume |
| `make status` | Show current worktree status |
| `make list` | List all dotfiles containers |

## Common Workflows

### Initial Setup

```bash
make build   # Build image
make shell   # Enter development environment
```

### Test Configuration Changes

After editing dotfiles on host:

```bash
make shell
# Inside container:
source ~/.zshrc              # Reload zsh
tmux source ~/.tmux.conf     # Reload tmux (inside tmux)
:source $MYVIMRC             # Reload neovim (inside nvim)
```

### Reset Environment

```bash
make clean   # Remove container and volume
make build   # Rebuild image
make shell   # Enter fresh environment
```

## Container Architecture

- **Image**: `dotfiles:{worktree-name}`
- **Container**: `dotfiles-{worktree-name}`
- **Volume**: `dotfiles-{worktree-name}-home` (persists home directory)
- **Mount**: `~/.dotfiles` (read-only)

## Included Tools

- Neovim (stable)
- tmux 3.5
- zsh
- Node.js (latest LTS)
- Python3 + pynvim

## Troubleshooting

### Container won't start

1. Check status: `make status`
2. View logs: `docker logs dotfiles-{worktree-name}`
3. Rebuild: `make clean && make build`

### Changes not reflected

dotfiles are mounted read-only. Edit on host, then reload inside container.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.