Docker Manager
Docker Manager is a VS Code extension for managing the Docker resources in the current development environment. It uses the Docker CLI from the extension host and never executes Webview-supplied shell commands.
Features
- Docker daemon connection and version information
- Container dashboard, filtering, lifecycle actions, inspection, logs and terminals
- Image listing, pull, build, tag, inspection and removal
- Volume listing, creation, inspection and unused-volume removal
- Network listing, creation, inspection and removal
- Docker Compose project detection and lifecycle actions
- Container CPU, memory and network monitoring
- Activity Bar container view
- Confirmation dialogs for destructive operations
Requirements
- Visual Studio Code 1.90 or newer
- Docker CLI on
PATH
- Docker Desktop or Docker Engine
- Docker Compose V2 (
docker compose) for Compose features
Installation
npm install
npm run compile
code --extensionDevelopmentPath=$PWD
Press F5 in VS Code to launch an Extension Development Host.
To build a VSIX:
npm install
npm run compile
npx @vscode/vsce package
code --install-extension vendayx-docker-0.1.0.vsix
Usage
Open the Command Palette and run:
Docker Manager: Open Dashboard
Docker Manager: Refresh Resources
Docker Manager: List Containers
Docker Manager: List Images
Docker Manager: List Volumes
Docker Manager: List Networks
Docker Manager: Build Image
Docker Manager: Pull Image
Docker Manager: Open Container Logs
Docker Manager: Check Docker Connection
The dashboard is available from the Docker Manager Activity Bar entry.
Docker setup
Windows users should start Docker Desktop and wait until its engine reports running. Linux users should ensure Docker Engine is running and the current user has permission to access /var/run/docker.sock. Docker Manager does not change daemon permissions or Docker security settings.
Architecture
src/
extension.ts
commands/
providers/
services/
models/
utils/
media/
test/unit/
test/integration/
Docker operations run only in the extension host. The Webview sends fixed message types, and identifiers are validated before Docker or terminal operations. Process execution uses argument arrays rather than shell concatenation.
Testing
npm test
npm run compile
npm audit
Unit tests mock Docker process operations. Integration tests can be run only when Docker is available and are not required for the unit suite.
Troubleshooting
- Docker CLI not found: install Docker and add
docker to PATH.
- Daemon unavailable: start Docker Desktop or Docker Engine.
- Permission denied: review Docker socket or named-pipe permissions.
- Compose unavailable: install Docker Compose V2.
- No resources: confirm the Docker context is active and the daemon is running.
Roadmap
- Dockerode support as an alternate Engine transport
- Multi-context switching
- Compose service-level controls
- Persisted refresh intervals
- Advanced container resource charts
Contributing
Contributions should preserve strict Webview validation, fixed Docker handlers, argument-array process execution and confirmation-before-removal behavior.