# Deploy RouterOS Containers

RouterOS containers require device-mode, storage, VETH networking, and version-specific commands. This skill helps Claude, Codex, and Claude Code produce safer MikroTik container workflows.

## Install

```bash
npx skillstore add tikoci/routeros-container
```

## Metadata

- Status: approved
- Slug: tikoci-routeros-container
- Skillstore revision: r1
- Version status: missing
- Tree hash: d8818f8e959fc1877358f5b5ec9296b1fbe0b9684850478049cef1631f217910
- Author: tikoci
- GitHub username: tikoci
- License: MIT
- Repository: https://github.com/tikoci/routeros-skills/tree/main/routeros-container
- Ref: 36e07d5e13068e5be64447e8f20b427cf2cbd21a
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, network, filesystem
- Quality score: 70
- Public page: https://skillstore.pages.dev/skills/tikoci-routeros-container
- Manifest: https://skillstore.pages.dev/api/skills/tikoci-routeros-container/manifest

## Capabilities

- Explains RouterOS container prerequisites, device-mode confirmation, and package installation paths.
- Builds VETH, bridge, NAT, and port-forwarding workflows for container networking.
- Shows container environment variables, mounts, storage paths, and version-specific property names.
- Guides image pulls, local tar imports, and RouterOS architecture mapping.
- Outlines CLI and REST API lifecycle operations for list, start, stop, delete, and status checks.
- Compares manual container setup with the RouterOS /app YAML system.

## Use Cases

- Provision Edge Containers: Plan RouterOS package setup, storage, VETH interfaces, bridges, NAT, and container lifecycle commands.
- Automate REST Lifecycle Tasks: Design safer REST workflows for listing, starting, stopping, polling, and deleting RouterOS containers.
- Prepare Local Images: Map RouterOS architecture to image platforms and check local tar import requirements before deployment.

## Prompt Templates

### Check Prerequisites

```
I have a MikroTik router running RouterOS [version] on [architecture]. Help me check whether it can run containers and list the safe setup steps.
```

### Create Container Networking

```
Design a VETH, bridge, IP, and NAT plan for a RouterOS container that should expose [service] on port [port]. Include rollback notes.
```

### Deploy an Image

```
Help me deploy [image name] on RouterOS [version] using external storage [disk path]. Include env vars, mounts, and lifecycle commands.
```

### Automate with REST

```
Create a least-privilege REST workflow for managing RouterOS containers from [language or tool]. Include polling, error handling, and credential safety.
```

## Limitations

- It does not verify commands against a live router unless a separate RouterOS tool is available.
- It cannot guarantee third-party container images are safe or compatible.
- Version details may need confirmation on RouterOS releases newer than the skill content.
- It does not replace RouterOS backups, lab testing, or change-control procedures.

## Best Practices

- Confirm RouterOS version and architecture before selecting package, image, and property names.
- Use external storage for container roots and volumes to protect internal flash.
- Use dedicated credentials, secure management networks, and backups before REST or firewall changes.

## Anti Patterns

- Copying examples with default admin credentials or placeholder secrets.
- Running containers from untrusted registries without pinning or review.
- Changing device-mode, NAT, or bridge settings on production routers without a rollback plan.

## Security Audit

- Audited at: 2026-07-07T06:50:34.829\+00:00
- Summary: The static command, network, filesystem, obfuscation, and reconnaissance hits are mostly Markdown examples or reference links, not executable behavior in the skill. No prompt injection or malicious exfiltration intent was found. One semantic issue remains: the REST API sample demonstrates plaintext Basic authentication with a default admin account.

## Stats

- Views: 117
- Downloads: 13
- Favorites: 0
- Popularity score: 0