+0
Daily
9,078
stars
1,070
forks
223
watchers
253
prs
406
issues
67
releases
README
A minimal Ubuntu base image modified for Docker-friendliness
_Baseimage-docker only consumes 8.3 MB RAM and is much more powerful than Busybox or Alpine. See why below._
Baseimage-docker is a special Docker image that is configured for correct use within Docker containers. It is Ubuntu, plus:
Modifications for Docker-friendliness.
Administration tools that are especially useful in the context of Docker.
Mechanisms for easily running multiple processes, without violating the Docker philosophy.
You can use it as a base for your own Docker images.
Baseimage-docker is available for pulling from the Docker registry and GHCR (GitHub Container Registry)!
What are the problems with the stock Ubuntu base image?
Ubuntu is not designed to be run inside Docker. Its init system, Upstart, assumes that it's running on either real hardware or virtualized hardware, but not inside a Docker container. But inside a container you don't want a full system; you want a minimal system. Configuring that minimal system for use within a container has many strange corner cases that are hard to get right if you are not intimately familiar with the Unix system model. This can cause a lot of strange problems.
Baseimage-docker gets everything right. The "Contents" section describes all the things that it modifies.
Why use baseimage-docker?
You can configure the stock ubuntu image yourself from your Dockerfile, so why bother using baseimage-docker?
Configuring the base system for Docker-friendliness is no easy task. As stated before, there are many corner cases. By the time that you've gotten all that right, you've reinvented baseimage-docker. Using baseimage-docker will save you from this effort.
It reduces the time needed to write a correct Dockerfile. You won't have to worry about the base system and you can focus on the stack and the app.
It reduces the time needed to run docker build, allowing you to iterate your Dockerfile more quickly.
It reduces download time during redeploys. Docker only needs to download the base image once: during the first deploy. On every subsequent deploys, only the changes you make on top of the base image are downloaded.
-----------------------------------------
Related resources:
Website |
Github |
Docker registry |
Discussion forum |
Twitter |
Blog
Table of contents
What's inside the image?
Overview
Wait, I thought Docker is about running a single process in a container?
Does Baseimage-docker advocate "fat containers" or "treating containers as VMs"?
Inspecting baseimage-docker
Using baseimage-docker as base image
Getting started
Adding additional daemons
Running scripts during container startup
Environment variables
Centrally defining your own environment variables
Environment variable dumps
Modifying environment variables
Security
System logging
Upgrading the operating system inside the container
Container administration
RunniDiscussions
#658Stepping down as maintainer1 comments · 2026-03-29#649noble-1.0.10 comments · 2025-03-15#644Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "--enable-insecure-key": executable file not found in $PATH: unknown.0 comments · 2024-12-08#626Welcome to baseimage-docker Discussions!0 comments · 2023-07-27
Latest release
resolute-1.0.25 resolute-1.0.25 2026-11-15Automated weekly security rebuild of resolute-1.0.24 with latest ubuntu:26.04 packages. Images pushed: - phusion/baseimage:resolute-1.0.25 - phusion/baseimage:resolute - ghcr.io/phusion/baseimage:resolute-1.0.25 - ghcr.io/phusion/baseimage:resolute