A lightweight, stupid simple, web-based Docker container start/stop UI for LAN environments.

Security notice: FastDock has no user authentication. It is designed for internal/LAN use only and must be deployed behind a VPN or in a trusted network. Mounting /var/run/docker.sock grants full control over the Docker host. See Security and SECURITY.md.

Desktop — container grid with status indicators

Mobile — responsive layout

_{Edit modal — rename containers and assign custom icons}

• Features
• Quick Start
• Installation
  • Docker Compose (recommended)
  • Node.js / npm
  • PM2 (production)
• Configuration
• Usage
• API Reference
• Security
• Limitations
• Contributing
• License
• Acknowledgements

Container Management

• Start and stop containers with a single click
• Real-time status indicators (running / stopped)
• Search containers by name

Multi-Server Support

• Manage containers across multiple local and remote Docker hosts
• Add, edit, and delete server configurations
• Per-server container views with clear server labels

Customization

• Assign custom display names to containers
• Upload custom icons (PNG, JPG, GIF, WebP, SVG — max 2 MB)
• Search and download icons from the selfh.st/icons library

Interface

• Responsive design — works on desktop, tablet, and mobile
• Configurable grid layout (1–3 columns)
• Sorting options (running first, alphabetical)
• Persistent preferences via localStorage

git clone https://github.com/totomusu/fastdock.git
cd fastdock
docker compose up -d --build

Open http://<your-server-ip>:3080 in a browser.

FastDock runs as a container but requires access to the host Docker daemon via the socket mount.

git clone https://github.com/totomusu/fastdock.git
cd fastdock
docker compose up -d --build

• Settings and uploaded icons persist in ./data (mounted to /app/data).
• The default port is 3080. Override it in docker-compose.yml or via the PORT environment variable.

macOS / Windows: Docker Desktop mounts the socket into its Linux VM, so FastDock controls that VM's containers — not host OS processes.

Prerequisites: Node.js ≥ 16.0.0, Docker daemon running locally.

git clone https://github.com/totomusu/fastdock.git
cd fastdock
npm install
npm start

For development with auto-reload:

npm run dev          # uses Node.js built-in --watch
npm run dev:nodemon  # uses nodemon

Do not run npm run dev server.js — server.js is already the entrypoint; extra arguments are forwarded and will cause an error.

npm install -g pm2
pm2 start ecosystem.config.js
pm2 save
pm2 startup   # auto-restart on system reboot

FastDock works behind Caddy, Nginx, or any standard reverse proxy. The server enables Express trust proxy so that rate limiting works correctly with X-Forwarded-For headers.

Example Caddy block:

fastdock.internal {
    reverse_proxy localhost:3080
}

Verify the socket is accessible before starting:

ls -la /var/run/docker.sock

1. Select a server — use the dropdown to switch between local and remote Docker hosts.
2. View containers — all containers for the selected server are shown as cards.
3. Start / Stop — click the button on any container card.
4. Edit — click the pencil icon to open the edit modal.

1. Click the pencil icon on any container card.
2. Set a custom display name.
3. Upload a custom icon or search for one by name (sourced from selfh.st/icons).
4. Click Save.

Supported upload formats: PNG, JPG, GIF, WebP, SVG. Maximum size: 2 MB.

1. Click + next to the server selector to add a remote server.
2. Enter a name, address (e.g. http://192.168.1.5), and port.
3. Use the pencil or trash icons next to existing servers to edit or remove them.

FastDock implements the following mitigations:

Despite these measures, FastDock has no authentication layer. It must only be deployed in networks where all users are trusted. See SECURITY.md for the full security posture and responsible disclosure process.

• No user authentication — deploy in trusted networks only.
• No audit log of container start/stop operations.
• Single-instance only (no distributed state).

Contributions are welcome! Please read CONTRIBUTING.md before opening a pull request.

Quick steps:

1. Fork the repository.
2. Create a feature branch: git checkout -b feature/your-feature.
3. Commit your changes with a clear message.
4. Push and open a Pull Request against main.

For bug reports and feature requests, open a GitHub Issue.

Distributed under the GNU General Public License v3.0. See LICENSE for the full text.

• Dockerode — Docker API client for Node.js
• selfh.st/icons — icon library used for container icon search
• Helmet — Express security headers
• Multer — multipart file upload handling
• file-type — magic byte MIME validation