jwilder/dockerize

Utility to simplify running applications in docker containers

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 50 minutes ago
Added to GitGenius on September 13th, 2026
Created on October 13th, 2014
Open Issues & Pull Requests: 16 (+0)
GitHub issues: Enabled
Number of forks: 423
Total Stargazers: 5,208 (+0)
Total Subscribers: 84 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 24.4 days
Mean response time: 366.8 days
90th percentile: 1551.5 days
Tracked items: 43

Most active contributors

Sign in to see contributor activity.

How this project is maintained

Around half of the issues opened in the past year never receive a reply. Only 7% of issues opened in the past year have been closed. Three people close 95% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 1
New in 7 days: 1
Closed in 7 days: 1
Avg open age: 3,077 days
Stale 30+ days: 1
Stale 90+ days: 1

Recent activity

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

Top labels

  • feature request (3)
  • question (1)

Most active issues this week

Detailed Description

dockerize is a utility that simplifies running applications in Docker containers by automating configuration and dependency management at startup time.

The tool solves the problem of applications that cannot read configuration directly from environment variables or that log to files instead of stdout and stderr. dockerize works by wrapping your application's entrypoint to perform three key tasks before the main process starts: it generates configuration files from templates using environment variables, it tails specified log files to stdout or stderr for visibility through docker logs, and it waits for dependent services to become available over TCP, HTTP, or Unix sockets. This approach is particularly useful for legacy applications with rigid configuration requirements or non-standard logging behavior.

Developers should adopt dockerize when working with applications that require file-based configuration but need to be controlled through environment variables in containerized environments, or when applications log to files that should be visible through standard Docker logging. It suits projects using frameworks like SQLAlchemy that expect configuration in specific file formats, or web servers like nginx that write logs to filesystem paths. The tool is especially valuable in orchestrated environments where dependency ordering matters and you need to delay application startup until other services are ready.

The project maintains a stable codebase with prebuilt binaries available across multiple architectures including Linux variants and macOS. The tool is distributed as a standalone binary that can be added to container images, and a base Docker image is provided with dockerize already installed in the PATH for immediate use.