apocas/dockerode

Docker + Node = Dockerode (Node.js module for Docker's Remote API)

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 30 minutes ago
Added to GitGenius on September 14th, 2026
Created on August 29th, 2013
Open Issues & Pull Requests: 26 (+0)
GitHub issues: Enabled
Number of forks: 488
Total Stargazers: 4,948 (+0)
Total Subscribers: 62 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 12.0 days
Mean response time: 101.8 days
90th percentile: 257.9 days
Tracked items: 55

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 19
New in 7 days: 0
Closed in 7 days: 3
Avg open age: 759 days
Stale 30+ days: 16
Stale 90+ days: 16

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • stale (28)
  • enhancement (3)
  • external (2)
  • needs inspection (1)

Detailed Description

Dockerode is a Node.js module that provides programmatic access to Docker's Remote API.

The tool solves the problem of controlling Docker from Node.js applications by wrapping the Docker Remote API in a JavaScript interface. It allows developers to manage containers, images, networks, volumes, and other Docker resources directly from Node code without shelling out to the Docker CLI. The module communicates with the Docker daemon through its HTTP API, exposing Docker operations as JavaScript methods and promises.

Dockerode suits projects where Docker automation needs to be integrated into a Node.js application—such as container orchestration tools, deployment systems, testing frameworks, or applications that need to spawn and manage containers programmatically. It works with both local Docker daemons and remote Docker hosts by accepting connection configuration. The module is appropriate for developers who want to avoid subprocess calls to the Docker CLI and prefer a native JavaScript API for Docker operations.

The project shows moderate maintenance activity with a typical response time of one to two weeks for issues and pull requests. Work in the issue tracker centers on enhancement requests, external dependencies, and items requiring inspection, suggesting the maintainer prioritizes feature additions and careful evaluation of incoming work rather than rapid issue closure.